-
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
Support API Profile in Bicep #851
Labels
Milestone
Comments
Related to some of the discussions happening in #516 We'd like to solve a few different scenarios with apiProfile. We will need to support this property to maintain parity for stack specifically, as you note. |
i just updated all my arm templates to use api Profile. Realized I broke my bicep decompiles. :-( |
sorry about that! we'll take a note to add this to known limitations. Will resolve this issue as part of #622 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
ARM Template engine supports specifying API Profile instead of specifying API version for each resource type.
ARM RP manifest supplies a map of api profile : api version for each resource type (only for the resource types supported in azure stack). Template engine uses this map to infer the api version to use from the api profile name
Here is a sample template
https://github.com/Azure/AzureStack-QuickStart-Templates/blob/master/101-vm-linux-create/azuredeploy.json#L4
Describe the solution you'd like
Bicep should support specifying api profile instead of specifying api version for each resource type
The text was updated successfully, but these errors were encountered: