-
Notifications
You must be signed in to change notification settings - Fork 742
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.
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
Using latest api version of a resource #1002
Comments
Thanks for raising this! We have #622 which is similar, but I don't think covers the ability to get the 'latest' at runtime. Some things to point out about API versioning in ARM:
So generally, our feeling on this is that we want to discourage people from picking up the API version at runtime and instead encourage pinning to a version and making the explicit decision to upgrade. That being said, we definitely see the need to simplify the syntax, know whether you're on the latest, and have an easy path to upgrade if you're not and want to be - currently we're thinking of addressing this with #622. Does that make sense for your use case? |
@stan-sz - any thoughts on the above? otherwise, I think we will plan to close this one |
Thanks for the thorough explanation, @anthony-c-martin. |
Also related to #516 |
In ARM template it's possible to not hardcode the API version for a given resource but dynamically (at 'run time') detect the latest api available for a resource:
(note - the ordering is not guaranteed and sorting is not available, thus the
first()
not necessarily returns the latest available, usually it does)In bicep this is not possible:
Can such scenario be supported in bicep? Is this something ARM template disallows by-design?
The text was updated successfully, but these errors were encountered: