Added update-metadata tool

[raych1]

This is the design spec

Overview of the changes:
Standardized response and process handling:

• Added extension methods to create standardized success and failure responses for package operations.
• Extended the ISpecGenSdkConfigHelper interface for creating and executing repo-configured processes with standardized error handling and response formatting.

Language-specific package update services:

• Added the ILanguagePackageUpdate interface

[Copilot]

Pull Request Overview

This PR introduces a new MetadataUpdateTool for updating package metadata files in Azure SDK packages, along with supporting infrastructure including a ProcessConfigurationService, ResponseFactory, and language-specific package update implementations. The changes also refactor the configuration helper to support multiple configuration types beyond just build operations.

Key changes:

• Added MetadataUpdateTool with configurable script or language-specific update logic
• Introduced ProcessConfigurationService to centralize process execution logic
• Extended SpecGenSdkConfigHelper to support multiple configuration types (Build, UpdateChangelog, UpdateVersion, UpdateMetadata, UpdateCi)
• Added language-specific package update service interface and stub implementations for all supported languages

Reviewed Changes

Copilot reviewed 16 out of 16 changed files in this pull request and generated 16 comments.

Show a summary per file

File	Description
SdkBuildTool.cs	Updated to use refactored configuration helper with new enum types
MetadataUpdateTool.cs	New tool implementing metadata update functionality with script-based or language-specific fallback logic
ServiceRegistrations.cs	Registered new services and language-specific package update implementations
ProcessConfigurationService.cs	New service centralizing process creation and execution with standardized response handling
LanguageService.cs	Enhanced with GetPackageInfo method and moved to Services namespace
IProcessConfigurationService.cs	Interface for the new process configuration service
ResponseFactory.cs	Factory for creating standardized success/failure responses
IResponseFactory.cs	Interface for the response factory
SpecGenSdkConfigHelper.cs	Refactored to support multiple configuration types and improved logging
PackageResponseBase.cs	Updated namespace import
Language-specific PackageUpdate classes	Stub implementations with NotImplementedException for future development
ILanguagePackageUpdate.cs	Interface defining package update operations

Comments suppressed due to low confidence (1)

tools/azsdk-cli/Azure.Sdk.Tools.Cli/Services/ProcessConfigurationService.cs:1

• Using await Task.CompletedTask before throwing an exception is unnecessary and serves no purpose. The await statement should be removed, and the method can simply throw the NotImplementedException directly. This pattern appears in all language-specific PackageUpdate classes.

using Azure.Sdk.Tools.Cli.Models;

[haolingdong-msft]

Thanks @raych1 for sending this PR to me and for putting the code together! But both the spec PR and Ben's PR are not merged and agreed by all. This PR is already imlementation. Should it pending on spec PR and Ben's PR be merged?

I was advised to first refer to spec PR for language integration details, and then refer to Ben's PR on integration, now refer to this PR. But all PRs are not agreed by all. I'm afraid I am quite confused and unclear on how to integrate with you at this point. Shanghai side work is pending on a clear agreement on integration.

We may like to see:

• an official and clear email, or a comment in this PR (rather than instant message 😢 ) to get it agreed by all stakeholders to show the integration approach for each language, as the design changed force and back.
• an example on how to integrate with AzureCLI if we are using scripts, see this comment: #12761 (comment). Shanghai side language owners may prefer script approach.

We are waiting for above information and for this PR to be approved by all stakeholders to start Shanghai side work.

/cc @lirenhe @lmazuel @maririos

[haolingdong-msft]

To @raych1: Shanghai mgmt sdk language owners prefer to use the script approach to integrate, as

• some command has sdk repo dependency
• script approach is faster to implement
• increases velocity, if language owners want to fix bugs, the fix takes effect immediately after merging to sdk repo, we don't need to wait for Azure.CLI code to be released.

We are waiting for this PR to be merged to start our Shanghai side work to integrate.
/cc @lmazuel

[haolingdong-msft]

To unblock the merge :), since I will be OOF tmr and might not get the chance to review latest changes. But please resolve my comments above as it may block shanghai side work.

[weshaggard]

@haolingdong-msft @msyyc I'm working on taking over Ben's spec PR #12696 to come up with a new script interface design. In the meantime I've asked @raych1 to continue to use the existing swagger_to_sdk_config.json configuration mechanism he used for the build command. @raych1 do you have that documented anywhere? I see you have the schema but perhaps an example of these new options would be helpful. I've added a comment in your spec PR to add that information.

[raych1]

@haolingdong-msft @msyyc I'm working on taking over Ben's spec PR #12696 to come up with a new script interface design. In the meantime I've asked @raych1 to continue to use the existing swagger_to_sdk_config.json configuration mechanism he used for the build command. @raych1 do you have that documented anywhere? I see you have the schema but perhaps an example of these new options would be helpful. I've added a comment in your spec PR to add that information.

@haolingdong-msft @msyyc I've added the configuration section and sample to the spec For the script contract, please refer to the last section in the original Word design spec.

[Copilot]

Pull Request Overview

Copilot reviewed 19 out of 19 changed files in this pull request and generated 4 comments.

[weshaggard]

One more clean-up but otherwise looks

[haolingdong-msft]

@haolingdong-msft @msyyc I've added the configuration section and sample to #12563 For the script contract, please refer to the last section in the original Word design spec.

Thanks @raych1 and @weshaggard for the clarification! We will use the word format design for contract.

Thanks @raych1 for the code. Leave two questions. Just want to make sure our script integrates with the code well. Thank you!