{Edge Action} Add Edge Action support for 2025-09-01-preview and make edge action top level command #903
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tundwed
changed the title
kairu-ms
approved these changes
Nov 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Generate Azure CLI SDK for Edge Actions service (2025-09-01-preview API version), introducing az edge-action as a new top-level command group. Edge Actions enables customers to deploy and manage custom JavaScript code at the Azure Front Door edge for use cases like request/response manipulation, dynamic routing, and security filtering. This PR includes AAZ-generated commands for complete CRUD operations on Edge Actions, versions, deployment operations (deploy-version-code, get-version-code), execution filters, and version management (swap-default).