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
When passing configurations frequently it can be repetitive for a user to put the --config flag on every command.
A possible suggestion to improve this experience is to have a default hidden file (or just generally a file that is always referenced by default) that passes all configurations that is always respected by kube-linter unless a config file is explicitly passed. This way a user could set their default profile for exactly what they want to check for once and not have to pass the --config parameters each time they want to lint something. This would allow users to set default custom configurations and to turn on and off checks.
When passing configurations frequently it can be repetitive for a user to put the --config flag on every command.
A possible suggestion to improve this experience is to have a default hidden file (or just generally a file that is always referenced by default) that passes all configurations that is always respected by kube-linter unless a config file is explicitly passed. This way a user could set their default profile for exactly what they want to check for once and not have to pass the --config parameters each time they want to lint something. This would allow users to set default custom configurations and to turn on and off checks.
As an industry example, in Redis there is a hidden file .redisclirc that allows users to add some preferences to the command line interface. This can be found here: https://github.com/redis/redis/blob/5d0c6b08686d51d552bae7dbb640625cfc1d73db/src/redis-cli.c#L76
The text was updated successfully, but these errors were encountered: