We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be good to see chef_environment append to an environment so it is not just overwritten completely.
as in one recipe could in theory just add a specific context into the environment (for example in normal attributes)
then in another recipe to the same environment append a different context instead of overwriting all of normal attributes with what it decided.
Not sure if even feasible but never hurts to ask
The text was updated successfully, but these errors were encountered:
This feels like a "not right now"
The Chef::Resource#current_value API can probably be used to retrieve the environment, then update it, then execute the action to change it.
Sorry, something went wrong.
No branches or pull requests
It would be good to see chef_environment append to an environment so it is not just overwritten completely.
as in one recipe could in theory just add a specific context into the environment (for example in normal attributes)
then in another recipe to the same environment append a different context instead of overwriting all of normal attributes with what it decided.
Not sure if even feasible but never hurts to ask
The text was updated successfully, but these errors were encountered: