[RDBMS] Breaking Change: Parameter name updates. Improvements to Management Plane for MySQL and PostgreSQL#15363
[RDBMS] Breaking Change: Parameter name updates. Improvements to Management Plane for MySQL and PostgreSQL#15363
Conversation
ServerNameAvailability API to validate server names
…e-cli into mjain2/ppbugbash
Connect, test fixes, parameter and description updates
Rebasing on top of hotfix
|
Please merge this with a squash commit :) |
|
RDBMS |
e17a251 to
468dff9
Compare
|
/azp run |
|
Pull request contains merge conflicts. |
| c.argument('server_name', id_part='name', options_list=['--name', '-n'], arg_type=server_name_getter_arg_type) | ||
| c.argument('force', options_list=['--force'], action='store_true', | ||
| help='Delete the server without prompt') | ||
| c.argument('yes', options_list=['--yes', '-y'], action='store_true', |
There was a problem hiding this comment.
renaming parameters name is breaking change. could you explain why we need such renaming?
There was a problem hiding this comment.
we wanted to deleting align confirmation parameters same as deleting commands of other resources
There was a problem hiding this comment.
@Juliehzl have updated the PR description to reflect these changes. Our new service was just rolled out last week so usage is still low, so there is relatively low risk.
|
could you refine description part according to https://github.com/Azure/azure-cli/tree/dev/doc/authoring_command_modules#submitting-pull-requests? |
Made the update thanks! |
Juliehzl
left a comment
There was a problem hiding this comment.
Approve for the breaking change because there is little usages in past 30 days and service team request
Description
This PR improves existing commands for the 'Flexible Servers' APIs within the RDBMS component.
Breaking changes:
Parameter name changes
Why: PM requested change to make it clearer for customer. Documentation on our side will also be updated.
Why: Consistency across different delete prompt commands for customer experience.
Why: PM requested change for consistency
Why: PM requested for clearer & self-explanatory params for customer experience.
Changes include:
Testing Guide
To run tests (these cover existing commands and include new tests):
azdev test rdbms
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.