-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[devcenter] Fix examples and show-logs-by-operation command output #8431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Update project env type parameters
Fix environment def example and update style
Fix show logs
Fix integration tests
Fix gallery test
Fix gallery test
Fix gallery compute
Update to 2024-05-01-preview
Update version
Update data plane tests 2024-10-01-preview
Update help
Fix examples and show logs output
️✔️Azure CLI Extensions Breaking Change Test
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
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 |
|
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
[Release] Update index.json for extension [ devcenter-6.2.1 ] : https://dev.azure.com/msazure/One/_build/results?buildId=113804780&view=results |
…zure#8431) * Update project env type parameters * Fix environment def example and update style * Fix show logs * Fix spacing * Fix style error * Fix integraion tests * Fix gallery test * Fix gallery test * Fix gallery compute * Update * Update control plane * Update tests and vendored sdk for data plane API * Updates * Update tests * Update version * Update tests * Update log command to support escape characters * Update control plane to 2024-10-01-preview * Changes for force delete only * update api version * remove preview flag * Fix linter errors * Update control plane tests * Update tests * Update commands * Add project policy test * Update * add missing override * Update response * Add tests * Fix image name regex * Update version for Ignite * Update data plane tests * Update control plane tests * Fix control plane tests * Fix nsg * Update params * Update release version * Update data plane 2024-10-01-preview * Remove old dp code * Add devbox list * Add project,pool,schedule * Add devbox * Fix post, add snapshots * Fix post LRO * Add environments * Add additional cmds * Fix help * Fix params * Fix customization task validate * Linter and style fixes * Update version * Update version2 * Update dp tests * Add dev box tests * Add repair test * Add snapshot test * Add customization task test * Add customization group test * Add environment test * Update tests * Update help * Fix tests * Fix examples and show logs output --------- Co-authored-by: Erica Guthan <[email protected]>
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
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.