Azure/azure-iot-cli-extension v0.30.0b2

azure-iot 0.30.0b2

on GitHub

What's Changed

• chore: sync dev branch with release/cms_public_preview by @ketkimnaik in #785

• fix: pass cloud-specific credential_scopes by @cheatsheet1999 in #786

• feat(adr): add policy revoke-issuer & device CRUD/revoke by @HangyiWang in #788

• chore: merge dev into cms_public_preview_refresh by @cheatsheet1999 in #794

• chore: replace hardcoded canary ARM endpoint with dynamic cloud endpoint by @HangyiWang in #796

• chore: remove LRO workarounds for policy revokeIssuer and activateBYOR by @HangyiWang in #797

• chore: rename --enable-certificate-management parameter by @HangyiWang in #798

• fix: send non-nullable disable property in device revoke request by @HangyiWang in #799

• chore: increase cms dev version number for internal testing by @HangyiWang in #801

• chore: adjust CMS device integration test by @HangyiWang in #802

• chore: CMS preview refresh version update by @HangyiWang in #804

• fix: cleanup helper message format by @HangyiWang in #807

• policy revoke-issuer (az iot adr ns policy revoke-issuer): revokes the current CA (issuer) certificate for a namespace policy and triggers the service to generate a new one. Use this when the CA certificate is compromised or needs rotation.

• bring your own root / BYOR (--enable-byor / az iot adr ns policy activate-byor): enables customers to use their own root CA instead of a service-managed one.

• device revoke (az iot adr ns device revoke): revokes all active credentials for a specified device in a namespace. The device must re-authenticate and obtain new credentials. Use --disable to also prevent the device from obtaining new credentials (sets device enabled state to false).

Full Changelog: v0.30.0b1...v0.30.0b2