Closed roryprimrose closed 1 year ago
Is this an actual problem or are you just getting this on --version
? Are the plugins not installed/running correctly?
It isn't blocking anything as the tflint still runs on the following command. So this only happens on the --version
call where it isn't picking up the installed plugins. So it isn't an operational problem but just emitting errors into the build log. You can see from the log that init is pulling down the plugins and running tflint is using them. It is just that version is freaking out that it can't find the plugins.
Ok cool, we can fix the issue with --version
, just trying to make sure it's actually isolated there per the title and not affecting the bare command.
The original issue is solved by setting --config
with --version
:
$ tflint --config=path/to/file --init
$ tflint --config=path/to/file --version
$ tflint --config=path/to/file
It feels a bit odd that config is required to output the versions, but I don't see a good idea to get around this as the plugin is configured by a config file.
As for command option isolation, we'll work on that in #1618. Closing this issue. Thanks.
I am running tflint (version 0.33.1) in an Azure DevOps Ubuntu agent. I run the following commands in the pipeline in a PowerShell step:
Abbreviated, this runs
The build log contains the error
Failed to initialize plugins: Plugin azurerm not found. Did you run tflint --init?
when running--version
after--init
.