Customer feedback | clarity needed for optional parameters that are conditionally required #29478
Labels
app-service-networking
Auto-Assign
Auto assign by bot
Data Factory
Functions
az functionapp
Monitor
az monitor
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
RBAC
az role
Service Attention
This issue is responsible by Azure service team.
Similar-Issue
Web Apps
az webapp
Summary
We have a recurring theme in our customer verbatims that optional parameters are required. See example verbatims in the the table below. There is some information given in error handling, but we need better clarity in our autogenerated content.
The misunderstanding might be coming from the following:
required
andoptional
.optional
heading.Request
We either need a third parameter category of
conditional
or similar, and/or we need our engineering teams to take advantage of thelong-summary
property and provide this useful information.Customer suggestion azDO link: https://ceapex.visualstudio.com/Engineering/_workitems/edit/987623 (Permission is required to access.)
Related GitHub filtered query links
Because GitHub issues and customer feedback comes in all shapes and sizes, these links should be considered "90% accurate" for "customer feedback on conditional parameters".
Azure/azure-cli
GitHub issues about optional parameters
GitHub issues about required parameters
Azure/azure-cli-extensions
GitHub issues about optional parameters
GitHub issues about required parameters
Example customer verbatims:
Disclaimer:
This suggestion assumes there is no customer error in this feedback, just a misunderstanding of when an optional parameter is required.
The text was updated successfully, but these errors were encountered: