-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rotate passwords for AVS 2020-07-17-preview #12290
Conversation
Hi, @ctaggart Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com |
Hi, @ctaggart your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). cc @ |
Swagger Validation Report
|
Rule | Message |
---|---|
1033 - RemovedProperty |
The new version is missing a property found in the old version. Was 'vcenterPassword' renamed or removed? New: Microsoft.AVS/preview/2020-07-17-preview/vmware.json#L3995:7 Old: Microsoft.AVS/preview/2020-07-17-preview/vmware.json#L3909:7 |
1033 - RemovedProperty |
The new version is missing a property found in the old version. Was 'nsxtPassword' renamed or removed? New: Microsoft.AVS/preview/2020-07-17-preview/vmware.json#L3995:7 Old: Microsoft.AVS/preview/2020-07-17-preview/vmware.json#L3909:7 |
1038 - AddedPath |
The new version is adding a path that was not found in the old version. New: Microsoft.AVS/preview/2020-07-17-preview/vmware.json#L586:5 |
1038 - AddedPath |
The new version is adding a path that was not found in the old version. New: Microsoft.AVS/preview/2020-07-17-preview/vmware.json#L629:5 |
️️✔️
LintDiff succeeded [Detail] [Expand]
Validation passes for LintDiff.
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
[Staging] Cross Version BreakingChange (Base on preview version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
[Staging] Cross Version BreakingChange (Base on stable version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
Swagger Generation Artifacts
|
Hi @ctaggart, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
NewApiVersionRequired reason: |
specification/vmware/resource-manager/Microsoft.AVS/preview/2020-07-17-preview/vmware.json
Show resolved
Hide resolved
@filizt, thanks for the feedback! I added the 204 response in 0d2b704. I'd like to get ARM signoff on this, this week. I will do the internal breaking change meeting on Monday (internal work item 9068467). |
@ctaggart The changes in the PR looks good from ARM perspective but official sign off will wait until breaking changes board's approval. |
@filizt & @zhenglaizhang, the breaking change has been reviewed and approved. Please approve & merge. |
ARM Signed off |
@msyyc @ArcturusZhang pls help take a look at python or go sdk breaking changes respectively |
@zhenglaizhang, we do not have any SDKs published for this API version. We do not intend to publish SDKs for this API version. We do need this merged soon. |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ctaggart unfortunately we have released one package of this api-version in go SDK v49.0.0 (https://github.com/Azure/azure-sdk-for-go/tree/v49.0.0/services/preview/avs/mgmt/2020-07-17-preview/avs).
If we did not want to release one package, we should not include this package in readme.go.md
(this was added in this PR #10866). Could you please remove it from readme.go.md
?
Considering that this package is a preview package, it is OK to remove it. But I suggest you double confirm about this.
Hey @ArcturusZhang, in that case, I'm okay with releasing the go SDK with these changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The breaking changes introduced in this PR are relative minor and considering those happen on a preview package, therefore those are acceptable
It's ok for Python |
This removes a breaking change in the 2020-07-17-preview to make it compatible with the 2020-03-20 API. I'm backporting it from the 2021-01-01-preview API in development. We are aware that this is a breaking change to the 2020-07-17-preview API and I will review it with the review board. No SDKs have been published for this API version. Rotate password functionality is not currently working in production. This will allow it to work.
This pull requests adds two actions for rotate passwords. Here is how the actions can be invoked:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Please ensure to add changelog with this PR by answering the following questions.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.