fix azconnectedk8s update --disable-proxy

[dimbleby]

pass empty "proxy" settings to cluster config DP, which will understand that to mean that proxy is being disabled.

cf https://msazure.visualstudio.com/One/_git/compute-HybridMgmt-ClusterConfigDP/pullrequest/11170292

@bavneetsingh16

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

[azure-client-tools-bot-prd]

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

[azure-client-tools-bot-prd]

Hi @dimbleby,
Since the current milestone time is less than 7 days, this pr will be reviewed in the next milestone.

[yonzhan]

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

[github-actions]

Hi @dimbleby

Release Suggestions

Module: connectedk8s

• Please log updates into to src/connectedk8s/HISTORY.rst
• Update VERSION to 1.10.1 in src/connectedk8s/setup.py

Notes

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