Open pirahawk opened 1 year ago
This is not a bicep issue. I would open a support case with the App Config team as to why the property is being ignored.
This is not a bicep issue. I would open a support case with the App Config team as to why the property is being ignored.
@alex-frankel Fair enough. From what I can see in the bicep documentation, I don't think the ability exists to be able to define the Label via the Bicep definition.
If the App config teams are responsible for maintaining this, happy to raise it on their board?
More discussion on this over here:
I added some DeploymentScripts to perform this task as a workaround for keys and feature flags.
https://github.com/Azure/bicep/discussions/9352#discussioncomment-6191816
Thanks @brwilkinson I will close this issue since it has been reported already and some workaround available.
@pirahawk it's moved to this types repo now. So it's fine to leave it open.
I am not clear why label is set to read only in ARM. All other properties are settable.
Plus it's settable via rest api commands.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @antcp, @AzureAppServiceCLI. Please see https://aka.ms/biceptypesinfo for troubleshooting help.
I have noticed that when creating Azure App Configuration Key-Values via Bicep, I cannot set a label for a configuration Key-Value pair declaratively via Bicep using the
Microsoft.AppConfiguration/configurationStores/keyValues@2023-03-01
resource type.For example consider the following Bicep template:
When this is run, I notice that the KV pair is created in Azure App Configuration instance, but the label is omitted.
As a contrast, running the equivalent Azure CLI command to do the same works fine:
May I please request that it would be awesome if there was Bicep support for being able to set labels, as being able to decorate KV pairs with labels for designated environments is a primary capability of Azure App Configuration.