Support sqlfluff configuration

[withinfocus]

Is your feature request related to a problem? Please describe.

sqlfluff support isn't configurable largely due to their lack of support for passing in a config file path. Now that sqlfluff/sqlfluff#1986 is in place the Super-Linter can follow its common practices for allowing a config file to be ... configured.

Describe the solution you'd like

Add the normal variables and passthrough to the linter so sqlfluff configuration files can be used.

Describe alternatives you've considered

Disabling the sqlfluff linter due to compatibility problems with the defaults.

[tunetheweb]

(one of the SQLFluff maintainers here)

Thanks for raising this for tracking, but this will need to wait until 0.9.0 is released with that additional configuration option.

BTW I use the GitHub Super Linter quite happily with SQLFluff simply by placing the .sqlfluff config file in the top level directory containing my SQL file (right up to root project if necessary).

So currently I have the following:

.github
sql
 └ .sqlfluff
 └ example.sql
 └ project
    └ example2.sql
src
 └ other code

But agree it would be good to also allow this to be configured similar to other GitHub Super Linter configuration files like so, for those that prefer, once SQLFluff 0.9.0 is released:

.github
 └ linters
    └ .sqlfluff
sql
 └ example.sql
 └ project
    └ example2.sql
src

But using the first option means SQLFluff is configurable right now, even without that.

[withinfocus]

Definitely on board with your second half there -- a lot of organizations (like mine) will want to have configuration for linting in a central location, and this generally better supports how the Super-Linter wants to work.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

If you're a maintainer, you can stop the bot to mark this issue as stale in the future by adding the O: backlog 🤖 label`.

[withinfocus]

Still a need.

[tunetheweb]

FYI opened #2361 to allow config file to be placed in usual location (.github/linters).