add breaking change message

[nguyenm2151]

---

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

Related command

acr import-pipeline create
acr export-pipeline create

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 @nguyenm2151,
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 @nguyenm2151

Release Suggestions

Module: acrtransfer

• Please log updates into to src/acrtransfer/HISTORY.rst
• Update VERSION to 1.1.1b1 in src/acrtransfer/setup.py

Notes

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

[Copilot]

Pull request overview

This PR adds breaking change warnings for the acr import-pipeline create and acr export-pipeline create commands to inform users that a new required parameter --storage-access-mode will be added in a future release.

Changes:

• Added a new _breaking_change.py file that registers breaking change notifications for two ACR pipeline create commands

[Copilot]

The _breaking_change module needs to be imported in init.py for the breaking change registrations to take effect. Similar to how _help is imported, add the following import to azext_acrtransfer/init.py:

from azext_acrtransfer._breaking_change import *  # pylint: disable=unused-import,unused-wildcard-import,wildcard-import

Without this import, the register_logic_breaking_change calls will never execute, and users won't see the breaking change warnings.