Chef Ideas

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!

Add optional `policy_version` to infrastructure header

Many orgs use CI/CD to build policyfiles. Many of those have a build version (1.2.3) for each policy_revision (hash).


Allow orgs to define a policy_version string in their policy that has the build-system policy version associated with the hash. If this attribute is present on a node, display it as "Policy Version" in the METADATA section of the Client run in the Infrastructure tab in Automate, underneath the "Policy Revision" hash.


This is a free-form field and is for display and user purposes only.

  • Ken MacLeod
  • May 7 2021
  • New
  • Attach files
  • Jeff Dean commented
    1 Dec 03:33pm

    Without some sort of version representation within a Policy I don't know if we'll ever be able to use them. Our Change Control folks would not allow unversioned releases.

  • Karl Fischer commented
    28 May 01:54pm

    I can just imagine sitting in a Change Control meeting a reading the SHA to a Project Manager