If always_update config is setup - Then only chef update (which does a chef install) #1931
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Right now if you specify always_update in your kitchen.yml - If the policyfile lock is incorrect such that the command chef install fails, the kitchen tests will fail.
Instead if you are specifying always_update it should just run the chef update command which behind the scenes also does a chef install.
This also makes it faster, currently it is doing chef install then running chef update which also calls install
Issues Resolved
N/A
Type of Change
Feat - this perhaps is a fix
Check List