feat: introduce --read-paths to threat PATH as a file containing manifest paths #241
+31
−10
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
Introducing --read-paths as a new boolean config option, defaulting to false.
When set to true, we would consider PATH as a file containing puppet manifests to lint, separated by newlines.
This is my first contribution here, so I dont't expect this to be accepted as-is, just let me know what should I improve/change to get this right.
Additional Context
We are using puppet-lint as part of our cicd pipelines, and we currently have to resort to xargsing each modified puppet manifest in and executing puppet-lint for each file.
With this change we would be able to specify a list of files to lint in a single puppet-lint execution
Checklist