-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[AutoRelease] t2-edgeorder-2021-07-27-26245 #19948
Conversation
[EdgeOrder] Update 2020-12-01-preview swagger and add readme files (Azure#14935) * new api changes (#1) * new api changes * referer url change * EdgeOrder 2020-12-01-preview Swagger changes (Azure#5) * readme changes * Swagger refresh and update examples * Change examples as per oav validations * Minor swagger modifications * Minor spacing adjustments * Set ModelAsString to true for enums and modify examples * Fix swagger lint validation error * Modify readme and examples * Modify readme.go.md * Update swagger * Minor prettier fix * Change python package version in readme * Fix spell check error Co-authored-by: sashanm <[email protected]>
Thank you for your contribution azclibot! We will review the pull request and get back to you soon. |
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run python - edgeorder - ci |
Azure Pipelines successfully started running 1 pipeline(s). |
Dev healthcareapis microsoft.healthcare apis 2022 10 01 preview (Azure#19948) * Adds base for updating Microsoft.HealthcareApis from version stable/2022-06-01 to version 2022-10-01-preview * Updates readme * Updates API version in new specs and examples * add analytics connector * add analytics connector example * fix error * fix error * fix error * fix error * remove 202 for create * fix bug * add discriminators * Add missing required type * remove 2 properties * remove additional properities * add long running operations * fix addition properties * fix name pattern * fix identity alert * revert workspace name change * fix location * fix warning * fix warning * fix LRO error * add async headers * merge from stable version Co-authored-by: Tong Wu (SH) <[email protected]>
https://github.com/Azure/sdk-release-request/issues/1739