[confcom] adding stopsignal, refactoring tests#6714
Merged
Conversation
…formats are changed
…not pretty printed
Refactor/test cases
…ng_policy changing print existing policy so it prints out the whole policy
changing api versions and getting rid of is_preview
…_default changing default value for allow_properties_access
adding stop signals
more information around errors with dmverity-vhd
setting version numbers for dependencies
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @SethHollandsworth, |
Collaborator
|
confcom |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
kairu-ms
approved these changes
Sep 5, 2023
Collaborator
|
[Release] Update index.json for extension [ confcom ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=88690&view=results |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adding stopsignal feature from docker, refactoring tests so they are easier to maintain, and pinning dependency versions. Also changing default value for allow_properties_access in policies.
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az confcom
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally?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.