-
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
[Hub Generated] Review request for Microsoft.DigitalTwins to add version stable/2020-10-31 #10653
[Hub Generated] Review request for Microsoft.DigitalTwins to add version stable/2020-10-31 #10653
Conversation
…20-03-01-preview to version 2020-10-31
…ttps://github.com/sjiherzig/azure-rest-api-specs into dev-digitaltwins-Microsoft.DigitalTwins-2020-10-31
…ttps://github.com/sjiherzig/azure-rest-api-specs into dev-digitaltwins-Microsoft.DigitalTwins-2020-10-31
[Staging] Swagger Validation Report
️✔️ |
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 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
|
Validation tools were run, but an exception occurred when running the linter in OpenApi hub: x-ms-secret was not recognized as a valid extension when checking against the schema. |
@sjiherzig, do you plan to release SDKs for this version after merging this PR? Please update readme.md if your answer is yes. |
Azure Pipelines successfully started running 1 pipeline(s). |
Thanks! I've updated the readmes accordingly. |
@sjiherzig, 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. |
Changes looks good. Marked it as ARMSignedoff. |
@erich-wang What would be the next step? We're all set for merging in our changes, I think. |
@sjiherzig, I'm going to merge this PR, but I noticed that the API version is 2020-10-31, please let me know if this PR is ready to merge from service team perspective. |
@erich-wang I discussed it internally, and we are ready to merge! |
…ion stable/2020-10-31 (Azure#10653) * Adds base for updating Microsoft.DigitalTwins from version preview/2020-03-01-preview to version 2020-10-31 * Updates readme * Updates API version in new specs and examples * Aligned descriptions with GA controller models, and regex patterns in parameters * Update nullable attribute to x-nullable * Latest updates * Add x-ms-secret = true for endpoint PUT * Latest changes * Fix reference issue * Simplify operationResults * Update required property name * Update examples * Update provisioning states * Add 200OK response to delete endpoints * Adds suppression to readme * Adds suppression to readme * Fix operation list example * Add additional provisioning state for endpoints * Remove tags from endpoint * Address internal reviewer comments * Update x-ms-secret properties to be nullable * Adds suppression to readme * Update examples with more realistic obfuscated connection strings * Adds suppression to readme * Adds suppression to readme * Adds suppression to readme * Run npm prettier on changes * Updated readmes
…into formrecognizer_regeneration * 'master' of https://github.com/Azure/azure-rest-api-specs: [Hub Generated] Review request for Microsoft.DigitalTwins to add version stable/2020-10-31 (Azure#10653) [SRP] Introduce 2020-08-01-preview version. (Azure#10570) Update Readmes for Python for Automanage (Azure#10633) Incident entities (Azure#10648) Fix Billing Swagger (Azure#10276) Connected machine az cli (Azure#10640) [Azure Stack] Updates to Azs.AzureBridge.Admin spec (Azure#9035)
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
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.