generated from terraform-linters/tflint-ruleset-template
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Provider aliases #331
Comments
You can use a custom logger for debugging. Logs via this logger are forwarded to TFLint. Depending on the log level, you can filter by |
Oh, I see. Thank you. I can see the log. |
Solved by #342 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Terraform supports defining multiple configurations for the same provider, and select which one to use on a per-resource or per-module basis.
https://www.terraform.io/language/providers/configuration#alias-multiple-provider-configurations
But tflint doesn't support this, so even if multiple configurations are defined only one configuration is used.
This raises a problem in Deep Checking.
How to reproduce
.tflint.hcl
main.tf
This error occurs even if Key Pair and AMI exist in the region
ap-northeast-1
, because tflint gets resources fromus-east-1
using the aliasus-east-1
.Solution
Runner.AwsClient
to mapmap[string]*Client
and creates clients per Provider Configurationprovider
attribute and get the appropriate Client from map of clientsI tried to implement this, but it doesn't work well yet.
#332
I'll appreciate if you help me.
It is difficult to debug because I don't know how to output the plugin log.
Reference
The text was updated successfully, but these errors were encountered: