Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support config files with well-known file names #49

Open
viswajithiii opened this issue Oct 30, 2020 · 1 comment
Open

Support config files with well-known file names #49

viswajithiii opened this issue Oct 30, 2020 · 1 comment
Labels
decision pending Still deciding whether this is something we should do enhancement New feature or request needs design Indicates that the proposed enhancement needs more thought on design

Comments

@viswajithiii
Copy link
Contributor

Right now, the config file is passed using the --config flag to kube-linter lint. In practice, however, users may want to have different configs (with different custom checks and different lists of enabled checks) for different apps, which may be in different directories or different Helm charts. Similar to .eslintrc files, we could support config files with a well-known filename, say .kube-linterrc, and have kube-linter lint automatically read them and merge them into the existing config as it walks directories.

@viswajithiii viswajithiii added enhancement New feature or request needs design Indicates that the proposed enhancement needs more thought on design decision pending Still deciding whether this is something we should do labels Oct 30, 2020
@bdsoha
Copy link

bdsoha commented Aug 14, 2023

A great addition to this issue would be allowing the search to also be based on an env variable:

export KUBE_LINTER_CONFIG=/path/to/the/config
kube-linter lint .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
decision pending Still deciding whether this is something we should do enhancement New feature or request needs design Indicates that the proposed enhancement needs more thought on design
Projects
None yet
Development

No branches or pull requests

2 participants