You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://xyproblem.info / Motivation: Somewhat related to #228: It's not currently possible to exclude files from a given directory. In the context of developing Kubernetes GitOps repository this is often an issue. The ability to run yamale on multiple individual files would address it.
The text was updated successfully, but these errors were encountered:
Can you provide the version of Yamale you're using and the error message you're seeing? I can run yamale on single files using the same syntax you gave with the latest release, 5.2.1.
thiagowfx
changed the title
Feature Request: Run yamale on a specific file
Feature Request: Run yamale on a specific set of files
Jun 24, 2024
My bad, you are right, Chris. For a single file, it works. The failure happens when you pass more than one file to it.
I got confused because this got surfaced in the context of pre-commit.com, and I had not realized that it was trying to pass more than one file to yamale.
I reworded the FR to support multiple files in addition to an individual one.
The documentation is also outdated ("PATH folder to validate. Default is current directory.").
I will send a PR iff I get spare cycles to do so.
thiagowfx
changed the title
Feature Request: Run yamale on a specific set of files
Feature Request: Ability to run yamale on multiple files
Jun 24, 2024
Observed: Currently it's only possible to run
yamale
in a directory, or for a single file.Expected: It should also be possible to run
yamale
on a given set of files.Example usage:
This currently fails with:
https://xyproblem.info / Motivation: Somewhat related to #228: It's not currently possible to exclude files from a given directory. In the context of developing Kubernetes GitOps repository this is often an issue. The ability to run
yamale
on multiple individual files would address it.The text was updated successfully, but these errors were encountered: