Skip to content
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

Merged
merged 3 commits into from
May 17, 2021
Merged

SQL - Add Resource Identity swagger to common v2 #14439

merged 3 commits into from
May 17, 2021

Conversation

viparek
Copy link
Contributor

@viparek viparek commented May 17, 2021

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.

  1. What's the purpose of the update?
    • new service onboarding
    • new API version
    • update existing version for new feature
    • update existing version to fix swagger quality issue in s360
    • [/] Other, please clarify - Updating an existing swagger to add resolve the naming issue that caused a breaking change.
  2. When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
  3. When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
  4. If it's an update to existing version, please select SDKs of specific language and CLIs that require refresh after swagger is published.
    • [ /] SDK of .NET (need service team to ensure code readiness)
    • [ /] SDK of Python
    • SDK of Java
    • SDK of Js
    • SDK of Go
    • [ /] PowerShell
    • CLI
    • Terraform
    • No, no need to refresh for updates in this PR

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.

    • Adding new API(s)
    • Adding a new API version
    • Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
    • Adding a new service
  • [/ ] 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.

  • Removing API(s) in stable version
  • Removing properties in stable version
  • Removing API version(s) in stable version
  • Updating API in stable or public preview version with Breaking Change Validation errors
  • Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

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.

@viparek viparek requested a review from bcham as a code owner May 17, 2021 21:47
@openapi-workflow-bot
Copy link

Hi, @viparek Thanks for your PR. I am workflow bot for review process. Here are some small tips.

  • Please ensure to do self-check against checklists in first PR comment.
  • PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging.
  • For specs comparison cross API versions, Use API Specs Comparison Report Generator
  • If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. How to fix?

  • Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com

    @openapi-workflow-bot
    Copy link

    [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.

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented May 17, 2021

    Swagger Validation Report

    ️️✔️BreakingChange succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️LintDiff succeeded [Detail] [Expand]
    Validation passes for LintDiff.
    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️ModelValidation succeeded [Detail] [Expand]
    Validation passes for ModelValidation.
    ️️✔️SemanticValidation succeeded [Detail] [Expand]
    Validation passes for SemanticValidation.
    ️️✔️Cross-Version Breaking Changes succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️️✔️[Staging] SDK Track2 Validation succeeded [Detail] [Expand]
    Validation passes for SDKTrack2Validation
    ️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
    Validation passes for PrettierCheck.
    ️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
    Validation passes for SpellCheck.
    ️️✔️[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
    Validation passes for Lint(RPaaS).
    Posted by Swagger Pipeline | How to fix these errors?

    @ghost ghost added the SQL label May 17, 2021
    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented May 17, 2021

    Swagger Generation Artifacts

    ️️✔️[Staging] ApiDocPreview succeeded [Detail] [Expand]
    ️⌛[Staging] SDK Breaking Change Tracking pending [Detail]
    ️️✔️ azure-sdk-for-net succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from 1c801aa. SDK Automation 14.0.0
      warn	Skip initScript due to not configured
      command	sudo apt-get install -y dotnet-sdk-5.0
      command	autorest --version=V2 --csharp --reflect-api-versions --license-header=MICROSOFT_MIT_NO_VERSION --use=@microsoft.azure/autorest.csharp@2.3.82 --csharp-sdks-folder=/home/vsts/work/1/s/azure-sdk-for-net/sdk ../azure-rest-api-specs/specification/sql/resource-manager/readme.md
      cmderr	[Autorest] realpath(): Permission denied
      cmderr	[Autorest] realpath(): Permission denied
      cmderr	[Autorest] realpath(): Permission denied
      cmderr	[Autorest] realpath(): Permission denied
      cmderr	[Autorest] realpath(): Permission denied
      cmderr	[Autorest] realpath(): Permission denied
    • ️✔️Microsoft.Azure.Management.Sql [View full logs]  [Release SDK Changes]
    ️⚠️ azure-sdk-for-python warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from 1c801aa. SDK Automation 14.0.0
      command	sh scripts/automation_init.sh ../azure-sdk-for-python_tmp/initInput.json ../azure-sdk-for-python_tmp/initOutput.json
      cmderr	[automation_init.sh] ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
      cmderr	[automation_init.sh] azure-mgmt-core 1.2.2 requires azure-core<2.0.0,>=1.9.0, but you have azure-core 1.6.0 which is incompatible.
      cmderr	[automation_init.sh] ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
      cmderr	[automation_init.sh] azure-mgmt-core 1.2.2 requires azure-core<2.0.0,>=1.9.0, but you have azure-core 1.6.0 which is incompatible.
      cmderr	[automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
      command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
    • ️✔️azure-mgmt-sql [View full logs]  [Release SDK Changes]
      info	[Changelog]
    ️⚠️ azure-sdk-for-python-track2 warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from 1c801aa. SDK Automation 14.0.0
      command	sh scripts/automation_init.sh ../azure-sdk-for-python_tmp/initInput.json ../azure-sdk-for-python_tmp/initOutput.json
      cmderr	[automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
      command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
    • ️✔️track2_azure-mgmt-sql [View full logs]  [Release SDK Changes]
      info	[Changelog]
    ️⚠️ azure-sdk-for-java warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from 1c801aa. SDK Automation 14.0.0
      command	./eng/mgmt/automation/init.sh ../azure-sdk-for-java_tmp/initInput.json ../azure-sdk-for-java_tmp/initOutput.json
      command	./eng/mgmt/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json
      cmderr	[generate.py] 2021-05-24 02:31:10 INFO [VERSION][Not Found] cannot find version for "com.azure.resourcemanager:azure-resourcemanager-sql-generated"
      cmderr	[generate.py] 2021-05-24 02:31:10 INFO [VERSION][Not Found] cannot find stable version, current version "1.0.0-beta.1"
      cmderr	[generate.py] 2021-05-24 02:31:10 INFO autorest --version=3.1.3 --use=@autorest/java@4.0.28 --java.azure-libraries-for-java-folder=/home/vsts/work/1/s/azure-sdk-for-java --java.output-folder=/home/vsts/work/1/s/azure-sdk-for-java/sdk/sql/azure-resourcemanager-sql-generated --java.namespace=com.azure.resourcemanager.sql.generated   --java --pipeline.modelerfour.additional-checks=false --pipeline.modelerfour.lenient-model-deduplication=true --azure-arm --verbose --sdk-integration --fluent=lite --java.fluent=lite --java.license-header=MICROSOFT_MIT_SMALL ../azure-rest-api-specs/specification/sql/resource-manager/readme.md
      cmderr	[generate.py] 2021-05-24 02:35:08 INFO [CI][Success] Write to ci.yml
      cmderr	[generate.py] 2021-05-24 02:35:08 INFO [POM][Process] dealing with pom.xml
      cmderr	[generate.py] 2021-05-24 02:35:08 INFO [POM][Skip] pom already has module azure-resourcemanager-sql-generated
      cmderr	[generate.py] 2021-05-24 02:35:08 INFO [POM][Success] Write to pom.xml
      cmderr	[generate.py] 2021-05-24 02:35:08 INFO [POM][Process] dealing with root pom
      cmderr	[generate.py] 2021-05-24 02:35:08 INFO [POM][Success] Write to root pom
    • ️✔️azure-resourcemanager-sql-generated [View full logs]  [Release SDK Changes]
      cmderr	[Inst] 2021-05-24 02:40:49 DEBUG Got artifact_id: azure-resourcemanager-sql-generated
      cmderr	[Inst] 2021-05-24 02:40:49 DEBUG Got artifact: pom.xml
      cmderr	[Inst] 2021-05-24 02:40:49 DEBUG Got artifact: azure-resourcemanager-sql-generated-1.0.0-beta.1-sources.jar
      cmderr	[Inst] 2021-05-24 02:40:49 DEBUG Got artifact: azure-resourcemanager-sql-generated-1.0.0-beta.1.jar
      cmderr	[Inst] 2021-05-24 02:40:49 DEBUG Match jar package: azure-resourcemanager-sql-generated-1.0.0-beta.1.jar
      cmderr	[Inst] 2021-05-24 02:40:49 DEBUG output: {"full": "```sh\ncurl -L \"https://portal.azure-devex-tools.com/api/sdk-dl-pub?p=Azure/14439/azure-sdk-for-java/azure-resourcemanager-sql-generated/azure-resourcemanager-sql-generated-1.0.0-beta.1.jar\" -o azure-resourcemanager-sql-generated-1.0.0-beta.1.jar\nmvn install:install-file -DgroupId=com.azure.resourcemanager -DartifactId=azure-resourcemanager-sql-generated -Dversion=1.0.0-beta.0 -Dfile=azure-resourcemanager-sql-generated-1.0.0-beta.1.jar -Dpackaging=jar -DgeneratePom=true
      ```"}
    ️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from 1c801aa. SDK Automation 14.0.0
      command	sh ./initScript.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json
      command	go run ./tools/generator/main.go ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json
    • ️✔️sql/mgmt/2014-04-01/sql [View full logs]  [Release SDK Changes]
      info	[Changelog] No exported changes
    • ️✔️preview/sql/mgmt/v4.0/sql [View full logs]  [Release SDK Changes] Breaking Change Detected
      Only show 18 items here, please refer to log for details.
      info	[Changelog] - New struct `LongTermRetentionBackupsUpdateByResourceGroupFuture`
      info	[Changelog] - New struct `LongTermRetentionBackupsUpdateFuture`
      info	[Changelog] - New struct `LongTermRetentionOperationResultProperties`
      info	[Changelog] - New struct `LongTermRetentionPoliciesClient`
      info	[Changelog] - New struct `LongTermRetentionPoliciesCreateOrUpdateFuture`
      info	[Changelog] - New struct `LongTermRetentionPolicy`
      info	[Changelog] - New struct `LongTermRetentionPolicyListResult`
      info	[Changelog] - New struct `LongTermRetentionPolicyListResultIterator`
      info	[Changelog] - New struct `LongTermRetentionPolicyListResultPage`
      info	[Changelog] - New struct `UpdateLongTermRetentionBackupParameters`
      info	[Changelog] - New struct `UpdateLongTermRetentionBackupParametersProperties`
      info	[Changelog] - New field `RequestedBackupStorageRedundancy` in struct `DatabaseProperties`
      info	[Changelog] - New field `CurrentBackupStorageRedundancy` in struct `DatabaseProperties`
      info	[Changelog] - New field `BackupStorageRedundancy` in struct `LongTermRetentionBackupProperties`
      info	[Changelog] - New field `RequestedBackupStorageRedundancy` in struct `LongTermRetentionBackupProperties`
      info	[Changelog]
      info	[Changelog] Total 92 breaking change(s), 110 additive change(s).
      info	[Changelog]
    • ️✔️preview/sql/mgmt/v3.0/sql [View full logs]  [Release SDK Changes] Breaking Change Detected
      Only show 18 items here, please refer to log for details.
      info	[Changelog] - New function `ManagedInstancesClient.ListByManagedInstance(context.Context, string, string, *int32, string, string, string, QueryTimeGrainType, AggregationFunctionType, MetricType) (TopQueriesListResultPage, error)`
      info	[Changelog] - New function `QueryStatisticsProperties.MarshalJSON() ([]byte, error)`
      info	[Changelog] - New struct `ManagedInstancePecProperty`
      info	[Changelog] - New struct `ManagedInstancePrivateEndpointConnectionProperties`
      info	[Changelog] - New struct `ManagedInstancePrivateEndpointProperty`
      info	[Changelog] - New struct `QueryMetricInterval`
      info	[Changelog] - New struct `QueryMetricProperties`
      info	[Changelog] - New struct `QueryStatisticsProperties`
      info	[Changelog] - New struct `TopQueries`
      info	[Changelog] - New struct `TopQueriesListResult`
      info	[Changelog] - New struct `TopQueriesListResultIterator`
      info	[Changelog] - New struct `TopQueriesListResultPage`
      info	[Changelog] - New field `PrivateEndpointConnections` in struct `ManagedInstanceProperties`
      info	[Changelog] - New field `ZoneRedundant` in struct `ManagedInstanceProperties`
      info	[Changelog] - New field `Identity` in struct `ManagedInstanceUpdate`
      info	[Changelog]
      info	[Changelog] Total 20 breaking change(s), 70 additive change(s).
      info	[Changelog]
    • ️✔️preview/sql/mgmt/2018-06-01-preview/sql [View full logs]  [Release SDK Changes] Breaking Change Detected
      Only show 18 items here, please refer to log for details.
      info	[Changelog]
      info	[Changelog] - Const `None` type has been changed from `SensitivityLabelRank` to `IdentityType`
      info	[Changelog] - Const `High` has been removed
      info	[Changelog] - Const `Critical` has been removed
      info	[Changelog] - Const `Medium` has been removed
      info	[Changelog] - Const `Low` has been removed
      info	[Changelog]
      info	[Changelog] ### New Content
      info	[Changelog]
      info	[Changelog] - New const `SensitivityLabelRankLow`
      info	[Changelog] - New const `SensitivityLabelRankNone`
      info	[Changelog] - New const `SensitivityLabelRankMedium`
      info	[Changelog] - New const `UserAssigned`
      info	[Changelog] - New const `SensitivityLabelRankCritical`
      info	[Changelog] - New const `SensitivityLabelRankHigh`
      info	[Changelog]
      info	[Changelog] Total 5 breaking change(s), 6 additive change(s).
      info	[Changelog]
    • ️✔️preview/sql/mgmt/2017-10-01-preview/sql [View full logs]  [Release SDK Changes]
      info	[Changelog] No exported changes
    • ️✔️preview/sql/mgmt/2017-03-01-preview/sql [View full logs]  [Release SDK Changes] Breaking Change Detected
      Only show 18 items here, please refer to log for details.
      info	[Changelog]
      info	[Changelog] ### New Content
      info	[Changelog]
      info	[Changelog] - New const `PrimaryAggregationTypeMinimum`
      info	[Changelog] - New const `PrimaryAggregationTypeNone`
      info	[Changelog] - New const `PrimaryAggregationTypeTotal`
      info	[Changelog] - New const `BytesPerSecond`
      info	[Changelog] - New const `Percent`
      info	[Changelog] - New const `PrimaryAggregationTypeCount`
      info	[Changelog] - New const `PrimaryAggregationTypeAverage`
      info	[Changelog] - New const `Seconds`
      info	[Changelog] - New const `PrimaryAggregationTypeMaximum`
      info	[Changelog] - New const `Bytes`
      info	[Changelog] - New const `CountPerSecond`
      info	[Changelog] - New const `UserAssigned`
      info	[Changelog]
      info	[Changelog] Total 12 breaking change(s), 12 additive change(s).
      info	[Changelog]
    • ️✔️preview/sql/mgmt/2015-05-01-preview/sql [View full logs]  [Release SDK Changes] Breaking Change Detected
      Only show 18 items here, please refer to log for details.
      info	[Changelog]
      info	[Changelog] ### New Content
      info	[Changelog]
      info	[Changelog] - New const `Percent`
      info	[Changelog] - New const `PrimaryAggregationTypeAverage`
      info	[Changelog] - New const `UserAssigned`
      info	[Changelog] - New const `PrimaryAggregationTypeTotal`
      info	[Changelog] - New const `CountPerSecond`
      info	[Changelog] - New const `PrimaryAggregationTypeCount`
      info	[Changelog] - New const `PrimaryAggregationTypeMinimum`
      info	[Changelog] - New const `PrimaryAggregationTypeMaximum`
      info	[Changelog] - New const `Bytes`
      info	[Changelog] - New const `Seconds`
      info	[Changelog] - New const `PrimaryAggregationTypeNone`
      info	[Changelog] - New const `BytesPerSecond`
      info	[Changelog]
      info	[Changelog] Total 12 breaking change(s), 12 additive change(s).
      info	[Changelog]
    ️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from 1c801aa. SDK Automation 14.0.0
      warn	Skip initScript due to not configured
      command	autorest --version=V2 --typescript --license-header=MICROSOFT_MIT_NO_VERSION --use=@microsoft.azure/autorest.typescript@4.4.4 --typescript-sdks-folder=/home/vsts/work/1/s/azure-sdk-for-js/azure-sdk-for-js ../../azure-rest-api-specs/specification/sql/resource-manager/readme.md
    • ️✔️@azure/arm-sql [View full logs]  [Release SDK Changes]
      cmderr	[npmPack] loaded rollup.config.js with warnings
      cmderr	[npmPack] (!) Unused external imports
      cmderr	[npmPack] default imported from external module 'rollup' but never used
      cmderr	[npmPack] ./esm/sqlManagementClient.js → ./dist/arm-sql.js...
      cmderr	[npmPack] created ./dist/arm-sql.js in 2.3s
    ️️✔️ azure-resource-manager-schemas succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from 1c801aa. Schema Automation 14.0.0
      command	.sdkauto/initScript.sh ../azure-resource-manager-schemas_tmp/initInput.json ../azure-resource-manager-schemas_tmp/initOutput.json
      warn	File azure-resource-manager-schemas_tmp/initOutput.json not found to read
      command	.sdkauto/generateScript.sh ../azure-resource-manager-schemas_tmp/generateInput.json ../azure-resource-manager-schemas_tmp/generateOutput.json
    Posted by Swagger Pipeline | How to fix these errors?

    @ericshape
    Copy link
    Contributor

    /azp run

    @azure-pipelines
    Copy link

    Azure Pipelines successfully started running 1 pipeline(s).

    @jorgecotillo jorgecotillo added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label May 17, 2021
    @jorgecotillo
    Copy link
    Contributor

    Make sure to always select all items that apply from the checklist.

    Copy link
    Contributor

    @jamestao jamestao left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    LGTM

    @mikhailshilkov
    Copy link
    Contributor

    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...

    @ericshape
    Copy link
    Contributor

    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!
    We are sorry to break your pipeline due to the lack of a "breaking change" tag. We will be careful about it in the future.

    Here is why we did this breaking change:
    In the recent Swagger release for 2020-11-01-preview API, we modified the Server and Managed Instance resources to add User Assigned Identity. To maintain backward compatibility with old APIs we introduced a new ResourceIdentityWithUserAssignedIdentities common entity which extended the old ResourceIdentities common entity.
    Unfortunately, on releasing the NET SDK we realized that a lot of customers who would be consuming the new SDK will break since the Object Class Name is changing. In order to address this issue, we remapped this new entity to a new version of ResourceIdentity to make sure the class name remains the same. This will prevent breaking a lot of customers which depend on the server/managed instance resources and they will now not need to make code changes to consume the new SDK.

    @ericshape ericshape added Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 potential-sdk-breaking-change labels May 19, 2021
    @mikhailshilkov
    Copy link
    Contributor

    Thank you for the explanation and for labeling the issue as breaking.

    By the way, I noticed that the "broken" name ResourceIdentityWithUserAssignedIdentities has already propagated into the Python SDK: https://github.com/Azure/azure-sdk-for-python/blob/890a9e4472a330d306d45c8e649042125ed16145/sdk/sql/azure-mgmt-sql/azure/mgmt/sql/models/_models.py#L11282

    What is the plan there?

    @ericshape
    Copy link
    Contributor

    ericshape commented May 19, 2021

    Thank you for the explanation and for labeling the issue as breaking.

    By the way, I noticed that the "broken" name ResourceIdentityWithUserAssignedIdentities has already propagated into the Python SDK: https://github.com/Azure/azure-sdk-for-python/blob/890a9e4472a330d306d45c8e649042125ed16145/sdk/sql/azure-mgmt-sql/azure/mgmt/sql/models/_models.py#L11282

    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.
    In case you don't know, our API/SDK/Clients have dependency:
    .NET SDK is upstream of Powershell.
    Python SDK is upstream of Azure CLI.

                                                                     |--> .NET SDK ***  --> powershell ***
     generate swagger from SQL DB internal repo -> API specs repo ---
                                                                     |--> python SDK (auto) ---> Azure CLI***
    
    
    *** manually, fix failed tests in corresponding repos, pass reviews
    

    @RAY-316
    Copy link
    Contributor

    RAY-316 commented May 24, 2021

    /azp run

    @ericshape
    Copy link
    Contributor

    Thank you for the explanation and for labeling the issue as breaking.

    By the way, I noticed that the "broken" name ResourceIdentityWithUserAssignedIdentities has already propagated into the Python SDK: https://github.com/Azure/azure-sdk-for-python/blob/890a9e4472a330d306d45c8e649042125ed16145/sdk/sql/azure-mgmt-sql/azure/mgmt/sql/models/_models.py#L11282

    What is the plan there?

    @mikhailalmeida
    We have had the latest Python SDK with the latest changes (include this PR).
    https://pypi.org/project/azure-mgmt-sql/0.29.0/#history
    0.29.0 for track1

    mkarmark pushed a commit to mkarmark/azure-rest-api-specs that referenced this pull request Jul 21, 2021
    * Add Resource Identity swagger to common v2
    
    * Change version number
    
    * Changed version num. Removed parameters
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review CI-BreakingChange-Go potential-sdk-breaking-change SQL
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    8 participants