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!


Kindly request implementation of

  • Guest
  • Oct 10 2019
  • Planned
  • Attach files
  • Tim Smith commented
    10 Feb, 2021 03:05am

    This is one of the important github issues we've identified for our upcoming Test Kitchen work. Thanks for raising this. We'll see what we can do.

  • Joshua O'Brien commented
    24 Jul, 2020 02:13pm

    Going to defer conversation to the github issue moving forward

  • Joshua O'Brien commented
    30 Oct, 2019 08:11pm

    This has been triaged by the client team. Changing status to "Researching"

  • Guest commented
    10 Oct, 2019 06:33pm

    Describe the Enhancement:

    I would like an install strategy of 'version' or whatever word makes most sense. As an example, for the Chef product.....the following actions would be expected for each version setting
    14 -> if latest 14 is not installed, install latest 14.x.x
    14.12 -> if latest 14.12 is not installed, install latest 14.12.x
    14.14.14 -> if this exact version is not installed, install 14.14.14

    Describe the Need:

    From personal experience, the need is for a test-kitchen situations where the user

    1. has to deal with Chef baked into an image
    2. desires a different version of Chef to be tested with, perhaps as different set of suites for example
    3. would reduce testing times by not having to download/install a version every time using the :always workaround

    Current Alternative

    Use the :always strategy, which is lots of extra work for scenarios involving one or more restarts and a good number of test suites.

    Arguably, this could be classified as a bug of the 'intent' of 'once'.   With the 'once' strategy I would definitely expect the 'skip completely if already installed' if I  don't specify a version.  But if I have a version specified, i'd expect it to install that version once, as described above/in github issue.