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
I'm trying to use a wrapper powershell script that calls sqlfluff instead of calling it directly, but I can't get it to work.
(The main reason for using a wrapper is that I would to make sure the user has the same version of sqlfluff installed as the CI/CD pipeline)
As a minimal example I tried this:
I made a simple wrapper script bin\sqlfluff.ps1 that does just this:
sqlfluff $args
(I tried with @args too)
When I call the script from the terminal, it seems to work as expected.
When I set the plugin's "Executable Path" to "sqlfluff", the plugin works fine.
When I set "Executable Path" to "bin\does_not_exists.ps1", I get an "executable not found" error message.
When I set "Executable Path" to "bin\sqlfluff.ps1", I don't get that message, but the plugin does not seem to work. Nothing happen, reformating files has no effect, etc.
I could not find any log or error message, and I have no idea what is wrong with my script (I'm more a bash person than powershell).
Help would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
I have a similar issue: I'm trying to run the docker image of sqlfluff via a bash script rather than my team having to each install python and sqlfluff.
Hi,
First, thanks for the nice plugin!
I'm trying to use a wrapper powershell script that calls sqlfluff instead of calling it directly, but I can't get it to work.
(The main reason for using a wrapper is that I would to make sure the user has the same version of sqlfluff installed as the CI/CD pipeline)
As a minimal example I tried this:
bin\sqlfluff.ps1
that does just this:(I tried with
@args
too)I could not find any log or error message, and I have no idea what is wrong with my script (I'm more a bash person than powershell).
Help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: