{Elastic-SAN} az elastic-san volume-group create/update: Add warning for CRC data integration check

[calvinhzy]

---

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

Related command

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]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[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]

CodeGen Tools Feedback Collection

Thank 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

[github-actions]

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

[Copilot]

Pull Request Overview

This PR adds user warnings related to the new CRC data integrity check flag for Elastic SAN volume groups and prepares the extension for release.

• Introduces warnings in create and update flows when --enforce-data-integrity-check-for-iscsi is set or unset
• Bumps extension version to 1.3.1b1
• Updates HISTORY.rst with the new release entry

Reviewed Changes

Copilot reviewed 3 out of 8 changed files in this pull request and generated 2 comments.

File	Description
src/elastic-san/setup.py	Bumped extension version to 1.3.1b1
src/elastic-san/azext_elastic_san/custom.py	Added logger.warning messages for the CRC data integration flag
src/elastic-san/HISTORY.rst	Added release history entry for version 1.3.1b1

Comments suppressed due to low confidence (1)

src/elastic-san/azext_elastic_san/custom.py:45

• There are no tests verifying that the new warning messages are emitted when the CRC flag is toggled; consider adding unit tests to assert the correct warnings for both enabled and disabled scenarios.

        if has_value(args.EnforceDataIntegrityCheckForIscsi) and args.EnforceDataIntegrityCheckForIscsi:

[Copilot]

The warning logic for CRC protection is duplicated in both create and update handlers; consider extracting it into a shared helper function to reduce code duplication and simplify future updates.

[Copilot]

Per Azure best practices, consider invoking the azure_development-get_best_practices tool to ensure this CRC warning integration aligns with recommended Azure CLI extension guidelines.

[azclibot]

[Release] Update index.json for extension [ elastic-san-1.3.1b1 ] : https://dev.azure.com/msazure/One/_build/results?buildId=128805219&view=results