-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
[PublicPreviewReadiness] The errors property in the MoveResourceProperties should be readonly. #10554
Conversation
[Staging] Swagger Validation Report
❌ |
Rule | Message |
---|---|
1029 - ReadonlyPropertyChanged |
The read only property has changed from 'false' to 'true'. New: Microsoft.Migrate/preview/2019-10-01-preview/regionmovecollection.json#L1173:9 Old: Microsoft.Migrate/preview/2019-10-01-preview/regionmovecollection.json#L1173:9 |
1032 - DifferentAllOf |
The new version has a different 'allOf' property than the previous one. New: Microsoft.Migrate/preview/2019-10-01-preview/regionmovecollection.json#L1173:9 Old: Microsoft.Migrate/preview/2019-10-01-preview/regionmovecollection.json#L1173:9 |
1033 - RemovedProperty |
The new version is missing a property found in the old version. Was 'properties' renamed or removed? Old: Microsoft.Migrate/preview/2019-10-01-preview/regionmovecollection.json#L1526:7 |
️️✔️
LintDiff [Detail]
️✔️
Validation passes for LintDiff.
️️✔️
Avocado [Detail]
️✔️
Validation passes for Avocado.
️️✔️
ModelValidation [Detail]
️✔️
Validation passes for ModelValidation.
️️✔️
SemanticValidation [Detail]
️✔️
Validation passes for SemanticValidation.
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-go - Release
|
Azure CLI Extension Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-resource-manager-schemas - Release
|
azure-sdk-for-net - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-python - Release
|
Trenton Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
@@ -1,6 +1,6 @@ | |||
{ | |||
"parameters": { | |||
"api-version": "2016-08-10", | |||
"api-version": "2019-10-01", |
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.
2019-10-01-preview?
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.
will take this.
a. Enhance the operation discovery with a relevant example. b. Fix the move resource properties error filed to be readonly.
4e4a448
to
000ad1c
Compare
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-python-track2 - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Breaking Changes Details The service is in private preview, and we are doing this fixes/improvements as part of public preview that is tentatively planned on 27th September 2020. We are also working on releasing auto generated powershell and SDK's so the swagger is being actively validated before public preview.
|
Can one of the admins verify this patch? |
a. Enhance the operation discovery with a relevant example.
b. Fix the move resource properties error filed to be readonly.
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
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.
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.
Please follow the link to find more details on PR review process.