-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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-resourcegraph-2021-04-25-38865 #18281
[AutoRelease] t2-resourcegraph-2021-04-25-38865 #18281
Conversation
Include the preview version of resource changes and resources history… (Azure#14084) * Include the preview version of resource changes and resources history APIs * Address the review feedback on releasing the new package version.
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: |
/check-enforcer override |
[Microsoft.DeviceUpdate] (Internal only) Added Private Endpoint Proxy Private Endpoint Update (Azure#18281) * (Internal only) Added Private Endpoint Proxy Private Endpoint Update * The existing resource also needs a change * Renamed example * Fixing more copy and paste errors * Removed read only, formatted new file * Move provisioning state inside proxy properties * Revert "Move provisioning state inside proxy properties" This reverts commit 414d0c687ca3420426606d0f4d54923ee58ddb82. * Moved proxy provisioning state into properties, try #2 * Moved proxy provisioning state into properties, try number 3 * Moved proxy provisioning state into properties, try number 4 * Moved Proxy provisioningState to top level, removed property bag * Fixed a naming error * Linter fixes * Removed flatten in Proxy properties * Reverted all provisioningState changes * Swapped properties to match the old swagger
https://github.com/Azure/sdk-release-request/issues/1479