Cfn-python-lint: Should we have a configuration file

[kddejong]

Description of issue.
With the new info rules we are starting to expand the amount of command line options and including, excluding rules. I'm wondering if we need to allow a configuration file we can read and use on execution.

For instance I want to have info rules always on but I don't want to type in the parameters every time. Because I'm lazy. Another use case as the rules expand it would be easier to disable certain rules with a config file instead of creating longer and longer command line parameters.

This would be the least precedence in parameters. Files and command line parameters will override the configuration file.

[fatbasstard]

Well.. We're so lazy we even created a wrapper application so internally we just run cb-cfn-lint template.yaml 😎

Like the idea though, let the audience decide based on the 👍 and 👎

[mtoftum]

I'd like to see support for a config file as long as it's not required to run and anything passed as arguments overrides whatever is in the config. That way it'll be minimal impact and can safely be ignored.

[cmmeyer]

I like this idea. I want a dot file I can put in the root of my directory that the linter picks up in the pipeline, but with the ability to lock-in overrides via the command line I'm executing via Travis, etc.

[Tro95]

I'd definitely like a config file, especially if I can set the template location(s) allowing me to just type cfn-lint with no arguments in the root of my project.

[kddejong]

Working to create a config file. Thanks for the input.