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
Use case: I have a repository with a single .tflint.hcl which contains the terraform and aws plugins. I'd like this file to be the single source of truth for how tflint is configured to run both locally and in CI.
I can almost achieve this by using the flags argument and passing --config to tflint directly:
However, since the value of the flags argument is never passed to the tflint --init command, the plugins are never installed, resulting in the following error:
Running tflint with reviewdog 🐶 ...
Failed to initialize plugins; Plugin `terraform` not found. Did you run `tflint --init`?
The text was updated successfully, but these errors were encountered:
I am also experiencing the same issue. As an alternative solution to those mentioned above, I would like to propose implementing a new parameter tflint_config.
In addition to tflint and tflint --init, tflint --version also accepts a --config argument. When --config is specified in tflint --version, it displays the version of the enabled plugins. Currently, action-tflint doesn't show the version of the plugins being used.
While the --config option is common in tflint, I believe it would be valuable to create it as a separate input for action-tflint.
Use case: I have a repository with a single
.tflint.hcl
which contains theterraform
andaws
plugins. I'd like this file to be the single source of truth for howtflint
is configured to run both locally and in CI.I can almost achieve this by using the
flags
argument and passing--config
totflint
directly:However, since the value of the
flags
argument is never passed to thetflint --init
command, the plugins are never installed, resulting in the following error:The text was updated successfully, but these errors were encountered: