Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Establish process for upgrading to new versions of AVM modules #4728

Open
JeffreyCA opened this issue Jan 23, 2025 · 0 comments
Open

Establish process for upgrading to new versions of AVM modules #4728

JeffreyCA opened this issue Jan 23, 2025 · 0 comments
Labels
Bicep compose composability

Comments

@JeffreyCA
Copy link
Contributor

JeffreyCA commented Jan 23, 2025 •
edited
Loading

Do we have a process yet for when/how we upgrade to new versions of AVM modules?

Originally posted by @wbreza in #4719 (comment)

That's a very good question. Do you have any suggestions? And if there's a need for something solid to be in-place today?

In general, it feels not too different to me than when we update api-version fħr any Azure resources, which boils down to when a version upgrade is required for a specific feature. Currently, this is mostly hidden away from the user so it wouldn't matter too much.

Originally posted by @weikanglim in #4719 (comment)
@JeffreyCA JeffreyCA changed the title Process for upgrading to new versions of AVM modules Establish process for upgrading to new versions of AVM modules Jan 23, 2025
@JeffreyCA JeffreyCA mentioned this issue Jan 23, 2025
Merged
@JeffreyCA JeffreyCA added Bicep compose composability labels Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bicep compose composability
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JeffreyCA