Automate update standalone repo from Azure/ResourceModules

[MariusStorhaug]

Description

As a consumer of the Azure/ResourceModules framework, I want an automated way to get updates into my repo.

[MariusStorhaug]

Suggestion to look into: https://github.com/Azure/AzOps-Accelerator/blob/main/.github/workflows/update.yml

[rahalan]

@MariusStorhaug please add as discussed a more detailed description

[AlexanderSehr]

Based on discussions:

Not strictly CARML-related. As such a lower-priority feature we could implement at some point in time, if time allows.

[MariusStorhaug]

From a discussion: Would they want updates every time a PR is approved, or just when a new release tag is associated?

More importantly, what do they do with the updates?

• Figure out which modules they’re using have been updated. And what the update is. And whether they want that update. And whether they want that now or later.
• Add their standard changes.
• Run their own tests of each updated module.
• Notify their CARML Solution Developers of the updated modules. Receive time frame for solution update using updated modules.
• Is this where package management and a private registry can help? By ensuring updates can’t break downstream developers and users. By separating CARML updates from internal module or solution updates.

[MariusStorhaug]

This is related to:

• #1587
• #1459

This issue is purely about automating the update process with a workflow/pipeline.