Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Jan 8, 2026

ARM (Control Plane) API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

spec_pr_review_workflow_diagram

Purpose of this PR

SDK generation for TypeSpec project specification/cdn/resource-manager/Microsoft.Cdn/EdgeActions targeting API version 2025-12-01-preview. TypeSpec updated to align with PR #39517 and all SDK PRs regenerated.

  • New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
  • New resource provider.
  • Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
  • Update existing version to fix OpenAPI spec quality issues in S360.
  • Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
  • Other, please clarify:
    • edit this with your clarification

SDK Generation Results

✅ Successfully Generated (5/5) - All Languages Completed

All SDK PRs have been successfully regenerated based on the updated TypeSpec from PR #39517 (commit: b1332d8).

Key Change: Removed Python custom client name to use default naming convention.

Language Package Pull Request Status
.NET Azure.ResourceManager.EdgeActions #54878 ✅ Success
Go sdk/resourcemanager/edgeactions/armedgeactions #25846 ✅ Success
Java azure-resourcemanager-edgeactions #47649 ✅ Success
JavaScript @azure/arm-edgeactions #37048 ✅ Success (Fixed!)
Python azure-mgmt-edgeactions #44582 ✅ Success

Notable Improvement: JavaScript SDK generation now succeeds. The previous TypeScript compilation errors were resolved by the TypeSpec updates from PR #39517.

Generation Pipeline Details

All SDK generation pipelines completed successfully:

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

  • I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
  • I have reviewed following Resource Provider guidelines, including
    ARM resource provider contract and
    REST guidelines (estimated time: 4 hours).
    I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
  • A release plan has been created. If not, please create one as it will help guide you through the REST API and SDK creation process.

Release Plan: 2040 (Work Item: 30082)

Additional information

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

  • First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
  • If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
  • To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
  • For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
    and https://aka.ms/ci-fix.
  • For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
  • If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
    This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
  • If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.
  • For guidance on SDK breaking change review, refer to https://aka.ms/ci-fix.
Original prompt

This section details on the original issue you should resolve

<issue_title>[TypeSpec] Generate SDK for TypeSpec project specification/cdn/resource-manager/Microsoft.Cdn/EdgeActions</issue_title>
<issue_description>## SDK generate request for TypeSpec project specification/cdn/resource-manager/Microsoft.Cdn/EdgeActions

Request to generate SDK by Copilot. Do not release SDK
SDK will be released later by service owner.

Release Plan: 2040
TypeSpec project path: specification/cdn/resource-manager/Microsoft.Cdn/EdgeActions
API spec pull request link: #38775
SDK release type: Beta
API spec version: 2025-12-01-preview
Spec Type: TypeSpec
Language: .NET,Go,Java,JavaScript,Python
Release plan work item ID: 30082

Contacts:
dannytundwe

Comments:
Generate SDK using Github copilot

Generate SDK for the TypeSpec project and update the generated SDK details in the release plan using release plan work item. Generate a summary and update it back in the linked GitHub issue once SDK pull requests are generated.
</issue_description>

Comments on the Issue (you are @copilot in this section)


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

@github-actions
Copy link

github-actions bot commented Jan 8, 2026

Next Steps to Merge

⌛ Please wait. Next steps to merge this PR are being evaluated by automation. ⌛

Comment generated by summarize-checks workflow run.

Copilot AI changed the title [WIP] Generate SDK for TypeSpec project specification/cdn/resource-manager/Microsoft.Cdn/EdgeActions SDK Generation for EdgeActions TypeSpec - 4 of 5 languages completed Jan 8, 2026
Copilot AI requested a review from azure-sdk January 8, 2026 02:08
@tundwed
Copy link
Member

tundwed commented Jan 15, 2026

@copilot i have updated the api sepc pull request link for the issue linked to this pr to be based on the commit #39517. Regenerate/updated all the 5 language PRs to be based on this commit

Copy link
Contributor Author

Copilot AI commented Jan 16, 2026

@copilot i have updated the api sepc pull request link for the issue linked to this pr to be based on the commit #39517. Regenerate/updated all the 5 ...

All 5 SDK PRs have been successfully regenerated based on PR #39517 (commit: 17b6781).

The TypeSpec change removed the Python custom client name. All pipelines completed successfully:

Copilot AI changed the title SDK Generation for EdgeActions TypeSpec - 4 of 5 languages completed SDK Generation for EdgeActions TypeSpec - All 5 languages completed (updated from PR #39517) Jan 16, 2026
Copilot AI requested a review from tundwed January 16, 2026 00:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[TypeSpec] Generate SDK for TypeSpec project specification/cdn/resource-manager/Microsoft.Cdn/EdgeActions

3 participants