Enable the tool to run checks against any arbitrary file provided by the user and skip regex pattern matching for those files.
Problem this Feature Will Solve
Currently, if a user passes a Docker Compose file to the program that does not match the regex file name pattern, it is ignored. For example:
In above case database.yaml exists in services directory and is a compose file, however the tool skips validation.
This feature will allow users to lint any file they wish, which is particularly useful for modular Docker Compose setups where services are stored in separate files and included in a central docker-compose.yaml file. See include:
Proposed Solution
Add a pre-search step to determine if the file passed by the user is a directory or a file. If it is a file, add it directly to the filesToCheck list without applying regex matching.
Alternatives Considered
None.
Additional Context
Feel free to reach out if you have any questions or need further assistance.
Feature Description
Enable the tool to run checks against any arbitrary file provided by the user and skip regex pattern matching for those files.
Problem this Feature Will Solve
Currently, if a user passes a Docker Compose file to the program that does not match the regex file name pattern, it is ignored. For example:
In above case
database.yaml
exists inservices
directory and is a compose file, however the tool skips validation.This feature will allow users to lint any file they wish, which is particularly useful for modular Docker Compose setups where services are stored in separate files and included in a central
docker-compose.yaml
file. Seeinclude:
Proposed Solution
Add a pre-search step to determine if the file passed by the user is a directory or a file. If it is a file, add it directly to the
filesToCheck
list without applying regex matching.Alternatives Considered
None.
Additional Context
Feel free to reach out if you have any questions or need further assistance.