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!
I can’t put a dollar value on this feature, but it will ultimately determine if the product is relevant in the market or not,
Chef prides itself in creating software that’s a joy to use for it’s users,
and happy users turn into Customers, happy customers turn into a in-the-trenches salesforce, I want to tell my customers why Chef is amazing and usually I have to compare it to other apps (Ansible), without inventory support it makes it a hard discussion.
Puppet Bolt has a inventory file
https://puppet.com/docs/bolt/latest/inventory_file.html
Salt (salt-ssh) goes one step further … where you can give it a sshconfig or Ansible inventory file
https://docs.saltstack.com/en/latest/ref/roster/all/index.html
If you have a universal inventory it can be reused for InSpec, chef-run and maybe remote deploys for Habitat.
Chef Inc you are our only hope™
Isn't Chef server database a ready inventory? We only need a way to specify a subset of servers, using a search query, for example.
Attachments Open full size
I think I don't get this feature of inventory. Isn't it what run_lists and roles provide, more or less? It would be a duplicate of features.
Attachments Open full size