Open
Conversation
Owner
I had implemented these originally, but after discussion with some Chef folks it turns out you can't really use these securely because the chef client can change them arbitrarily. I will take a look at the module conversion and metadata mapping. |
Author
In theory, this is correct. I'm using a lightwight proxy, written in go, in front of the chef server API to disallow changes to the run_list at the moment. I think there should be a big, fat, warning in the docs about this. If i find time, i will make the proxy releasable. |
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
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.
Improvements:
go-chef/chefFeatures: