-
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
OMode ModelAsString update to make it nullable and rearrangements to avoid breaking change in .Net #12963
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sandido
requested review from
dkulkarni-ms,
grizzlytheodore,
haagha,
hyonholee,
madewithsmiles and
MS-syh2qs
as code owners
February 11, 2021 21:00
Hi, @Sandido 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. [email protected] |
ghost
added
the
Compute
label
Feb 11, 2021
Swagger Validation Report
|
Rule | Message |
---|---|
PreCheck/DuplicateSchema |
"readme":"compute/resource-manager/readme.md", "tag":"package-2020-12-01", "details":"Duplicate Schema named PurchasePlan -- properties.promotionCode: undefined => "description":"The Offer Promotion Code.", "$ref":"#/components/schemas/schemas:1246" ; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
AutorestCore/Exception |
"readme":"compute/resource-manager/readme.md", "tag":"package-2020-12-01", "details":"Error: Plugin prechecker reported failure." |
"readme":"compute/resource-manager/readme.md", "tag":"package-2020-12-01", "details":"The schema 'ComputeOperationListResult' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"compute/resource-manager/readme.md", "tag":"package-2020-12-01", "details":"The schema 'ComputeOperationValue' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"compute/resource-manager/readme.md", "tag":"package-2020-12-01", "details":"The schema 'ComputeOperationValueDisplay' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"compute/resource-manager/readme.md", "tag":"package-2020-12-01", "details":"The schema 'DisallowedConfiguration' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"compute/resource-manager/readme.md", "tag":"package-2020-12-01", "details":"The schema 'RetrieveBootDiagnosticsDataResult' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"compute/resource-manager/readme.md", "tag":"package-2020-12-01", "details":"The schema 'InstanceViewStatus' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"compute/resource-manager/readme.md", "tag":"package-2020-12-01", "details":"The schema 'AvailabilitySetProperties' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"compute/resource-manager/readme.md", "tag":"package-2020-12-01", "details":"The schema 'AvailabilitySet' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
️⌛
[Staging] PrettierCheck pending [Detail]
️⌛
[Staging] SpellCheck pending [Detail]
Swagger Generation Artifacts
|
This was referenced Feb 11, 2021
Sandido
changed the title
OMode ModelAsString update to make it nullable
OMode ModelAsString update to make it nullable and rearrangements to avoid breaking change in .Net
Feb 11, 2021
11 tasks
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
hyonholee
approved these changes
Feb 12, 2021
trying to arrange for the one ForceDelete breaking change.
markcowl
approved these changes
Feb 16, 2021
Hi @Sandido, Your PR has some issues. Please fix the CI sequentially by following the order of
|
This was referenced Feb 17, 2021
mkarmark
pushed a commit
to mkarmark/azure-rest-api-specs
that referenced
this pull request
Jul 21, 2021
…avoid breaking change in .Net (Azure#12963) * Update compute.json * Update compute.json * Update compute.json * Update compute.json * Update compute.json trying to arrange for the one ForceDelete breaking change. * Update compute.json * Update compute.json
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Approved-OkToMerge
<valid label in PR review process>add this label when assignee approve to merge the updates
CI-BreakingChange-Go
Compute
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 Breaking Change 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.