-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Closed
Closed
Copy link
Labels
App ConfigurationAuto-AssignAuto assign by botAuto assign by botService AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.bugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.
Description
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
Metadata
Metadata
Assignees
Labels
App ConfigurationAuto-AssignAuto assign by botAuto assign by botService AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.bugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.
