-
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
Update readme files with Hybrid2020 Profile #11370
Conversation
## Update hybrid profile for - Authorization - Commerce - Compute - DataBoxEdge - Dns - EventHubs - IotHub - KeyVault - Monitor - Network - ResourceManager - Storage - Subscription - WebSites
[Staging] Swagger Validation Report
️✔️ |
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-js - Release
|
azure-sdk-for-python - Release
- Breaking Change detected in SDK
|
azure-sdk-for-python-track2 - Release
- Breaking Change detected in SDK
|
Azure CLI Extension Generation - Release
|
azure-resource-manager-schemas - Release
|
azure-sdk-for-go - 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
|
azure-sdk-for-net - Release
|
/azp run unifiedPipeline |
No pipelines are associated with this pull request. |
@HarveyLink, could you take a look at the code generation error? |
Automation pipeline failed with git push authentication, no idea why this step failed. Is there anyone i can reach for help? |
Talked with @PhoenixHe-msft , automation sdk errors are expected. Can we ignore these CI result? |
OK to merge with failure because it updates lot of readme.md |
## Update hybrid profile for - Authorization - Commerce - Compute - DataBoxEdge - Dns - EventHubs - IotHub - KeyVault - Monitor - Network - ResourceManager - Storage - Subscription - WebSites
Update hybrid profile for
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.
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.
Please follow the link to find more details on PR review process.