Azure Firewall Policy application rule new parameter - HTTP Headers to insert

[NiviShenker]

---

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

Related command

• network firewall policy rule-collection-group collection rule add/update: new parameter --http-headers-to-insert

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.

aaz PR: Azure/aaz#533

[azure-client-tools-bot-prd]

⚠️Azure CLI Extensions Breaking Change Test

⚠️azure-firewall

rule	cmd_name	rule_message	suggest_message
⚠️ 1006 - ParaAdd	network firewall policy rule-collection-group collection add-filter-collection	cmd network firewall policy rule-collection-group collection add-filter-collection added parameter http_headers_to_insert
⚠️ 1006 - ParaAdd	network firewall policy rule-collection-group collection rule add	cmd network firewall policy rule-collection-group collection rule add added parameter http_headers_to_insert
⚠️ 1006 - ParaAdd	network firewall policy rule-collection-group collection rule update	cmd network firewall policy rule-collection-group collection rule update added parameter http_headers_to_insert

[azure-client-tools-bot-prd]

Hi @NiviShenker,
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]

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

[necusjz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[necusjz]

Hi @NiviShenker, 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.

setup.py needs to be updated