Unhide NetworkMonitor resource, change prefix limit structure, and add device reboot tests

[cliffparsons]

Unhide NetworkMonitor resource, change prefix limit structure, and add device reboot tests.

---

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

Related command

az networkfabric networkmonitor create az networkfabric networkmonitor show az networkfabric networkmonitor list az networkfabric networkmonitor update az networkfabric networkmonitor delete

az networkfabric externalnetwork update --option-a-properties {... nativeIpv4PrefixLimit, nativeIpv6PrefixLimit ...} az networkfabric internalnetwork update --native-ipv4-prefix-limit --native-ipv6-prefix-limit

az networkfabric device reboot --reboot-type 'GracefulRebootWithZTP' az networkfabric device reboot --reboot-type 'GracefulRebootWithoutZTP' az networkfabric device reboot --reboot-type 'UngracefulRebootWithZTP' az networkfabric device reboot --reboot-type 'UngracefulRebootWithoutZTP'

General Guidelines

• [x] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• [x] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• [x] 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[bot]]

⚠️Azure CLI Extensions Breaking Change Test

⚠️managednetworkfabric

rule	cmd_name	rule_message	suggest_message
⚠️ 1011 - SubgroupAdd	networkfabric networkmonitor	sub group networkfabric networkmonitor added

[azure-client-tools-bot-prd[bot]]

Hi @cliffparsons, 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[bot]]

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

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

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

[necusjz]

/azp run

[azure-pipelines[bot]]

Azure Pipelines successfully started running 2 pipeline(s).

[necusjz]

/azp run

[azure-pipelines[bot]]

Azure Pipelines successfully started running 2 pipeline(s).