-
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
SQL - Add Resource Identity swagger to common v2 #14439
SQL - Add Resource Identity swagger to common v2 #14439
Conversation
Hi, @viparek 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. vsswagger@microsoft.com |
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
Swagger Validation Report
|
Swagger Generation Artifacts
|
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Make sure to always select all items that apply from the checklist. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I'm curious why this PR isn't marked as breaking. Effectively, it renames the type, which affects any typed downstream consumer. I understand it's made to revert the previous breaking change but I'd expect it to be clearly marked and approved as breaking. By the way, our native Pulumi Azure provider apparently ships changes faster than the Azure .NET SDK, so we already shipped the renamed types, and now this change is an actual break for us... |
@mikhailshilkov Thanks for your feedback! We appreciate it! Here is why we did this breaking change: |
Thank you for the explanation and for labeling the issue as breaking. By the way, I noticed that the "broken" name What is the plan there? |
Yes. once we have done the .NET SDK release and Powershell release, we will request a new python SDK release next week.
|
/azp run |
@mikhailalmeida |
* Add Resource Identity swagger to common v2 * Change version number * Changed version num. Removed parameters
This PR has the fix for a breaking change that was caused due to a change related to ResourceIdentity in Server API.
The .net checks failure is expected and will be fixed in an ongoing PR(Azure/azure-powershell#14997) which has a dependency on this PR.
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.