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. Thanks for collaborating with us!

Implement https://github.com/chef/mixlib-install/issues/295

Kindly request implementation of https://github.com/chef/mixlib-install/issues/295

Guest
Oct 10 2019
Researching

Chef Infra

2 Comments
2 Votes

Attach files

Enter a subject
Guest commented

10 Oct 18:33
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.
×
Attachments Open full size
Admin

Joshua O'Brien commented

30 Oct 20:11

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

×
Attachments Open full size