Remove empty .ansible-lint#442
Merged
Merged
Conversation
The .ansible-lint file contained only an empty YAML document ("---",
which parses to null) and had no effect on linting. The OSISM
ansible-lint container merges the per-repo .ansible-lint with the
image's baseline config; merging null with the baseline yields the
baseline, so this file changed nothing.
The current ansible-lint image masks the empty file by overwriting
/zuul/.ansible-lint with the merged config at lint time. The upcoming
read-only image no longer writes into the mount, so it would instead
lint this empty file and trip the non-skippable
schema[ansible-lint-config] rule, turning CI red for no real reason.
Removing the vestigial file keeps linting green and identical in
behaviour under both the old and new image.
AI-assisted: Claude Code
Signed-off-by: Roger Luethi <luethi@osism.tech>
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
3 participants
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.
What
Remove the repository's
.ansible-lint, which contained only an emptyYAML document (
---, parsing to null).Why
The file has no effect on linting. The OSISM
ansible-lintcontainermerges the per-repo
.ansible-lintwith the image's baseline config,and merging null with the baseline yields the baseline — so this file
changed nothing.
The current image masks the empty file by overwriting
/zuul/.ansible-lintwith the merged config at lint time. A plannedread-only rewrite of the
ansible-lintimage no longer writes into themount, so it would instead lint this empty file and trip the
non-skippable
schema[ansible-lint-config]rule, turning CI red for noreal reason. Removing the vestigial file keeps linting green and
behaviourally identical under both the old and the new image.
Rollout note
This should merge before (or together with) the read-only
ansible-lintimage change so CI stays green.
🤖 Generated with Claude Code