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!
When we install Chef Workstation it installs Chef Habitat as part of the install. This breaks our Development workstations and Jenkins Agents. Most of the time the version being installed is older than what we are running. Or if there was a problem with that specific version then we don't have it in our Onprem Habitat Builder which causes headaches trying to revert it back to the version we are currently using.
So if you can either not install Habitat by default or make an argument that works with brew, chocolatey, and RPM to omit the Habitat binary installation like --no-habitat it would keep us from having to meet with our developers to fix their workstations and fix broken builds when someone just installs the binary on our Jenkins Agent without knowing it will break our Habitat builds.