Move chef_license_key to protectedSettings for Azure Chef Extension - #4761
Merged
Merged
Conversation
Follows up on #4743 (chef_license_key public setting). Documents the fix in chef-partners/azure-chef-extension#413: chef_license_key should be set under protectedSettings, not public settings, since public settings/ARM parameters are readable via ARM deployment history and by anyone with Reader access to the VM extension resource — that exposes the Chef commercial license key well beyond the node itself. Public settings placement is still supported for backward compatibility (the extension logs a deprecation warning) but is being phased out. Signed-off-by: Thomas Powell <todd.powell@progress.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Todd Powell <todd.powell@progress.com>
✅ Deploy Preview for chef-web-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
tpowell-progress
added
the
ai-assisted
Updates the JSON deployment examples in the client 18/19 azure_chef_cli docs from the stale 1210.12 reference to the current release, 1210.15.11.1. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Thomas Powell <todd.powell@progress.com>
IanMadd
approved these changes
Sep 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Follows up on #4743, which documented
chef_license_keyas a public extension setting for the Azure Chef Extension.This documents the security fix in chef-partners/azure-chef-extension#413:
chef_license_keyshould be set underprotectedSettings, not public settings. Public settings/ARM deployment parameters are readable via ARM deployment history and by anyone with Reader access to the VM extension resource, which exposes the Chef commercial license key well beyond the node itself.chef_license_keyoption as deprecated (still supported for backward compatibility; the extension logs a deprecation warning).chef_license_keyunder the Protected settings section as the recommended location.Updated in both client 18 and client 19 docs.
Related: