We believe that the best way to build software is to do it in close collaboration with the people who use it. We invite you to submit your ideas using the form below. Please be sure to include the problem for which you are solving and the benefits of implementing the idea.
We do our best to implement as many Ideas as we can. Our Product team will evaluate all submitted ideas in a timely manner and will disposition each into one of the following categories: will integrate into the product roadmap, further research is needed, unlikely to implement.
Thanks for collaborating with us!
As a `chef-run` operator,
I would like an option that allows me to implement a `named_run_list` from a Policyfile,
So that I have the ability to use a single Policyfile that has the ability to `do many things`, which in turn will allow me to better orchestrate my adhoc tasks
For example, I would hope the option would look something like this:
`chef-run ssh://email@example.com web/ --named-run-list ‘disable-alerts’`
`chef-run ssh://firstname.lastname@example.org web/ --named-run-list ‘restart-service’`
`chef-run ssh://email@example.com web/ --named-run-list ‘enable-alerts’`
Assumed is the `web/` cookbook has a declared Policyfile.rb to more easily manage my dependencies ..
“But Greg, they can just define the recipe they want to use and it will autogenerate the run_list for you !!”
This is true, but there is also some demand that a `chef-run` operator be able to declare a user-defined Policyfile as a resource, and not have to clone and define a cookbook and/or recipes as the resource .. If this happens, IMO the only way to allow for mutli-purpose Policyfiles would be to allow the user to define a named run list as an option .. Maybe there is an alternative/better way ??