[AutoPR azure-resourcemanager-resources-deploymentstacks]-generated-from-SDK Generation - Java-5803514

[azure-sdk]

Configurations: 'specification/resources/resource-manager/Microsoft.Resources/deploymentStacks/tspconfig.yaml', API Version: 2025-07-01, SDK Release Type: stable, and CommitSHA: '652ad4cb131256f10a90ea2df207b38cf35d6671' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5803514 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. Release plan link: https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=0a321955-acfb-f011-8406-000d3a3ac981 Submitted by: kylealbert@microsoft.com

Release Plan Details

• Release Plan: https://aka.ms/sdk-release-planner?release-plan-id=0a321955-acfb-f011-8406-000d3a3ac981
  Spec pull request: [Microsoft.Resources] Deployment Stacks next stable API version 2025-07-01 azure-rest-api-specs#36828
  Spec API version: 2025-07-01

[Copilot]

Pull request overview

This is an automated SDK generation PR that updates the Azure Deployment Stacks resource manager library from AutoRest to TypeSpec code generation, introducing API version 2025-07-01. The PR represents a stable release (1.1.0) of the deployment stacks library with significant API enhancements.

Changes:

• Migration from AutoRest to TypeSpec code generator with updated attribution comments throughout
• Introduction of new WhatIf API operations for previewing deployment stack changes across subscription, resource group, and management group scopes
• Addition of deployment extension support with configuration models
• API breaking changes including removal of UnmanageAction* enum types replaced by unified DeploymentStacksDeleteDetachEnum

Reviewed changes

Copilot reviewed 97 out of 157 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
sdk/resources/azure-resourcemanager-resources/README.md	Updates version reference to 2.54.0-beta.1
sdk/resources/azure-resourcemanager-resources/CHANGELOG.md	Critical Issue: Incorrectly changes version to 1.1.0 (wrong library)
sdk/resources/azure-resourcemanager-resources-deploymentstacks/tsp-location.yaml	Adds TypeSpec location configuration
sdk/resources/azure-resourcemanager-resources-deploymentstacks/src/test/**	Adds comprehensive test coverage for new models and APIs
sdk/resources/azure-resourcemanager-resources-deploymentstacks/src/samples/**	Adds usage samples for new WhatIf APIs
sdk/resources/azure-resourcemanager-resources-deploymentstacks/src/main/**	Migrates to TypeSpec-generated code with new WhatIf and extension models
sdk/resources/azure-resourcemanager-resources-deploymentstacks/pom.xml	Updates to version 1.1.0 and TypeSpec attribution
eng/versioning/version_client.txt	Updates version tracking for deployment stacks library

[github-actions]

API Change Check

APIView identified API level changes in this PR and created the following API reviews

com.azure.resourcemanager:azure-resourcemanager-resources-deploymentstacks

[weidongxu-microsoft]

Hi @kalbert312 ,

I saw a break from your migration.

Before, in Swagger, there is 3 different enum (UnmanageActionResourceMode, UnmanageActionResourceGroupMode, UnmanageActionManagementGroupMode) for 3 parameters on DeploymentStacks_DeleteAtResourceGroup
https://github.com/Azure/azure-rest-api-specs/blob/2e5d83cb6120f521e833f7dfc56f6397592581dd/specification/resources/resource-manager/Microsoft.Resources/deploymentStacks/stable/2024-03-01/deploymentStacks.json#L1598-L1645

Now in TypeSpec, you only have 1 single DeploymentStacksDeleteDetachEnum for all 3 parameters.

This would be a break that likely cannot be mitigated by SDK. Are you sure this is correct?

PS: the naming DeploymentStacksDeleteDetachEnum is not great...

[kalbert312]

Hi @kalbert312 ,

I saw a break from your migration.

Before, in Swagger, there is 3 different enum (UnmanageActionResourceMode, UnmanageActionResourceGroupMode, UnmanageActionManagementGroupMode) for 3 parameters on DeploymentStacks_DeleteAtResourceGroup https://github.com/Azure/azure-rest-api-specs/blob/2e5d83cb6120f521e833f7dfc56f6397592581dd/specification/resources/resource-manager/Microsoft.Resources/deploymentStacks/stable/2024-03-01/deploymentStacks.json#L1598-L1645

Now in TypeSpec, you only have 1 single DeploymentStacksDeleteDetachEnum for all 3 parameters.

This would be a break that likely cannot be mitigated by SDK. Are you sure this is correct?

PS: the naming DeploymentStacksDeleteDetachEnum is not great...

I guess we can revert this to avoid customer confusion. The justification was that this is a single enum on the backend (which is named "CleanupActionType" which is a better name, I agree the name is bad). The justification for keeping them as separate types is if one of them diverged and accepted a different action type, this would be more easily scoped by the SDK.

[kalbert312]

Hi @kalbert312 ,
I saw a break from your migration.
Before, in Swagger, there is 3 different enum (UnmanageActionResourceMode, UnmanageActionResourceGroupMode, UnmanageActionManagementGroupMode) for 3 parameters on DeploymentStacks_DeleteAtResourceGroup https://github.com/Azure/azure-rest-api-specs/blob/2e5d83cb6120f521e833f7dfc56f6397592581dd/specification/resources/resource-manager/Microsoft.Resources/deploymentStacks/stable/2024-03-01/deploymentStacks.json#L1598-L1645
Now in TypeSpec, you only have 1 single DeploymentStacksDeleteDetachEnum for all 3 parameters.
This would be a break that likely cannot be mitigated by SDK. Are you sure this is correct?
PS: the naming DeploymentStacksDeleteDetachEnum is not great...

I guess we can revert this to avoid customer confusion. The justification was that this is a single enum on the backend (which is named "CleanupActionType" which is a better name, I agree the name is bad). The justification for keeping them as separate types is if one of them diverged and accepted a different action type, this would be more easily scoped by the SDK.

PR: Azure/azure-rest-api-specs#39987

[weidongxu-microsoft]

PR: Azure/azure-rest-api-specs#39987

Thanks. I've approved it. Also asked dev from other languages to comment (especially if any of them do not want this fix).

[weidongxu-microsoft]

.NET also doing a PR on specs repo Azure/azure-rest-api-specs#40198

[weidongxu-microsoft]

@kalbert312

PR ready. We need approval from service to merge.

[kalbert312]

@weidongxu-microsoft I want to confirm this includes the latest changes merged to rest api specs? We had to do some additional updates for .NET.

[weidongxu-microsoft]

.NET also doing a PR on specs repo Azure/azure-rest-api-specs#40198

@kalbert312

We've re-generated Java, after this .NET PR merged.

Do we have anything more?

[kalbert312]

.NET also doing a PR on specs repo Azure/azure-rest-api-specs#40198

@kalbert312

We've re-generated Java, after this .NET PR merged.

Do we have anything more?

No

[kalbert312]

@Azure/azure-java-sdk @ArthurMa1978 @haolingdong-msft @XiaofeiCao looking for approval.