{edge-action} Add edge-action extension for Edge Actions (2025-09-01-preview)#9439
Conversation
- Generated extension structure from AAZ - Added custom deploy-from-file command for file/zip deployment - Migrated 5 test scenarios with recordings from main CLI repo - Supports both file (.js) and zip deployment types - Auto-detection of deployment type from file extension
- Added linter_exclusions.yml for long parameter names - Added parameter help documentation for deploy-from-file command - Fixed line length in _params.py - Fixed pylint warning in custom.py (initialized encoded_content) - All tests passing (5/5) in playback mode
- Updated README.md with comprehensive usage examples - Clarified service is Azure Front Door Edge Actions (not generic CDN) - Added installation instructions and command examples - Updated setup.py description to mention Azure Front Door
- Added azext.summary following Azure CLI extension guidelines - Summary is concise (under 140 chars), specific, and uses correct branding - Verified with test_index.py validation
|
Validation for Breaking Change Starting...
Thanks for your contribution! |
|
Hi @tundwed, |
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
CodeGen Tools Feedback CollectionThank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey |
|
- Added command help with short and long summaries - Added 3 examples covering JavaScript, zip, and explicit deployment type - Fixes missing_command_example linter error
There was a problem hiding this comment.
Pull Request Overview
This PR adds a new CLI extension edge-action for managing Azure Front Door Edge Actions with API version 2025-09-01-preview. The extension provides commands for CRUD operations on edge actions and their versions, including deployment capabilities from files or zip archives.
Reviewed Changes
Copilot reviewed 51 out of 52 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| setup.py | Defines package metadata, dependencies, and classifiers for the edge-action extension |
| setup.cfg | Minimal setup configuration file |
| linter_exclusions.yml | Configures linter rule exclusions for long parameter names in execution-filter commands |
| test_edge_action.py | Comprehensive test suite covering CRUD operations, version management, and file/zip deployments |
| test_files/sample_edge_action.js | Sample JavaScript handler for testing edge action deployments |
| test_files/sample_edge_action.zip | Zipped version of the sample JavaScript file for testing zip deployments |
| test recordings/*.yaml | HTTP interaction recordings for test playback |
| init.py | Standard Python package initialization file |
- Moved 'import base64' from inside test method to top-level imports - Follows Python best practices for import organization - All imports now grouped at the top of the file
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
[Release] Update index.json for extension [ edge-action-1.0.0b1 ] : https://dev.azure.com/msazure/One/_build/results?buildId=144415687&view=results |
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
edge-action
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required)For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.jsonautomatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json.