-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{IoT} az iot hub policy renew-key
: Service-side HIS renewal of IoT Hub policy keys
#30334
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
@yonzhan @zhoxing-ms is there a reason this slipped to the next milestone? It's been open for 2 weeks and we really need this to go into a sooner release as the previous implementation causes service errors |
Due to Company-wise CCOA policy, we could not release until after Jan 6th. CloudShell and Azure PS also follow the same schedule. Sorry for the inconvenience caused. |
Understood - sorry I was out and didn't realize the CCOA was extended, thanks! |
May I ask if the changes are perceptible to users or not? |
@yanzhudd they are not - there is no change to the user. Instead of the CLI client locally generating a new key, the key is sent to the service as Object output is the same, no change to input, just a change of which side of the network the key is generated from. |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
az iot hub policy renew-key
: Service-side HIS renewal of IoT Hub policy keys
Related command
az iot hub policy renew-key
Description
This moves key generation for IoT Hub policy key renewals to the service side, rather than the client.
Testing Guide
This change is completely hidden from the user interface. The following example command should continue to renew policy keys for the IoT Hub:
az iot hub policy renew-key --name {policyName} --hub-name {hubName} --resource-group {resourceGroupName} --rk primary
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.