-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Automation] Adding command linting for extensions to ensure consistency. #282
Conversation
fail on error static check
|
||
# Install CLI & Dev Tools | ||
echo "Installing azure-cli-dev-tools and azure-cli..." | ||
pip install --pre azure-cli --extra-index-url https://azurecliprod.blob.core.windows.net/edge |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Print the az version so that we can check if the az is the latest build from the log.
scripts/ci/verify_linter.sh
Outdated
set +x # json output is too verbose | ||
public_index=$(az extension list-available -d) | ||
index_file=$(cat ./src/index.json) | ||
modified_extensions=$(python ./scripts/ci/index_changes.py "$index_file" "$public_index") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ugr, the three lines of code look ugly. Is there a better way?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll put this part of the code all into the python script
do get() in case of new entry
Upload model for `az monitor private-link-scope`
Closes: #205
-Linter verification occurs whenever index for a extension is modified, therefore publishing a new version of the extension.
-Teams will be expected to address linter problems with their extension when they next publish.