chore: stop tracking Policyfile lock - #613
Merged
Merged
Conversation
Slowest examplesTop 10 slowest examples (1.12 seconds, 46.74% of total time)
|
ramereth
approved these changes
Aug 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Policyfile.lock.jsonartefactChefSpec and Kitchen now resolve
Policyfile.rbat test time instead of depending on a committed lock. The fixture correction restores the searchedbe-1andbe-2backend servers across the integration matrix.Verification
chef install Policyfile.rbfrom a no-lock checkout - generated the ignored lock successfullycookstyle --no-server- 71 files, 0 offencesKITCHEN_LOCAL_YAML=kitchen.dokken.yml kitchen test config-backend-search-ubuntu-2404 --destroy=alwaysfrom a no-lock checkout - generated the lock, 7 controls, 0 failuresSecondary fix
The backend-search fixtures now set
chef_environmenttolocal. Without it, Chef search excludes both fixture nodes and the generated HAProxy configuration lacks the expected backend servers.