Value is not accepted when using az appconfig feature set --requirement-type #30619
Labels
App Configuration
Auto-Assign
Auto assign by bot
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
Service Attention
This issue is responsible by Azure service team.
Comments
george-lamprinos
added
the
bug
|
Thank you for opening this issue, we will look into it. |
microsoft-github-policy-service
bot
added
customer-reported
|
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @shenmuxiaosen, @avanigupta. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When creating a feature in App Configuration using azure cli, and specifying the requirement-type parameter, the generated feature flag is invalid because the requirement-type is using an invalid value ('all/any' instead of 'All/Any').
Related command
az appconfig feature set
--description "MyDescription"--requirement-type all
--feature MyFlag--name MyAppConfig `
--yes
Errors
The command succeeds, but the feature flag is invalid when viewing it in Azure Portal.
Issue script & Debug output
Expected behavior
A feature flag is being created that is valid, and uses the correct value for requirement type.
Environment Summary
{
"azure-cli": "2.67.0",
"azure-cli-core": "2.67.0",
"azure-cli-telemetry": "1.1.0"
}
Additional context
No response
The text was updated successfully, but these errors were encountered: