az aks prepared-image-specification

[jim-minter]

az aks prepared-image-specification

# if the subscription you're using doesn't have the feature flag, then register it:
az feature register --namespace Microsoft.ContainerService -n AKSPreparedImageSpecificationPreview
az provider register -n Microsoft.ContainerService --wait

# now wait a bit, I'm not entirely sure why this isn't immediate :-/

az extension add --upgrade --source https://jminter.blob.core.windows.net/pis/aks_preview-21.0.0b1.dev0+jimminter2-py2.py3-none-any.whl

az aks prepared-image-specification create -g "$RG" -n "$NAME" \
  --container-images alpine busybox \
  --customization-scripts '[{"name":"myscript","script":"/bin/true","scriptType":"Bash","executionPoint":"NodeImageBuildTime"}]' \
  --assign-identity /subcriptions/x/resourceGroups/y/providers/Microsoft.ManagedIdentity/userAssignedIdentities/z \
  --version "$VERSION" \
  --tags k=v \
  --no-wait

az aks prepared-image-specification list

az aks prepared-image-specification list -g "$RG"

az aks prepared-image-specification show -g "$RG" -n "$NAME"

az aks prepared-image-specification version list -g "$RG" --pis-name "$NAME"

az aks prepared-image-specification version show -g "$RG" --pis-name "$NAME" -n "$VERSION"

az aks prepared-image-specification update -g "$RG" -n "$NAME" --tags k=newv

az aks prepared-image-specification version delete -g "$RG" --pis-name "$NAME" -n "$VERSION" --yes --no-wait

az aks prepared-image-specification delete -g "$RG" -n "$NAME" --yes --no-wait

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

az aks prepared-image-specification

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

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.json automatically.
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.

[azure-client-tools-bot-prd]

Validation for Breaking Change Starting...

Thanks for your contribution!

[azure-client-tools-bot-prd]

Hi @jim-minter,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

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).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[github-actions]

Hi @jim-minter

Release Suggestions

Module: aks-preview

• Please log updates into to src/aks-preview/HISTORY.rst
• Update VERSION to 21.0.0b2 in src/aks-preview/setup.py

Notes

• For more info about extension versioning, please refer to Extension version schema

[github-actions]

Hi @jim-minter

Release Suggestions

Module: aks-preview

• Please log updates into to src/aks-preview/HISTORY.rst
• Update VERSION to 21.0.0b2 in src/aks-preview/setup.py

Notes

• For more info about extension versioning, please refer to Extension version schema