chef push always regenerates the revision id and Policyfile.lock.json

If the chef update and chef push commands always regenerate the Policyfile.lock.json file and the revision_id in it, make sure the Chef cookbook contains the chefignore file and it also references all possible Policyfile lock files:

# Policyfile #
##############
Policyfile.rb
*.lock.json

If a cookbook file changes, a new Policyfile.lock.json is generated during chef push.

chef update and chef push always check the cookbook files not listed in the chefignore file, and if there is a change, regenerate the Policyfile.lock.json including the revision_id element in it.

Leave a comment

Your email address will not be published. Required fields are marked *