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
Auto-completion with multiple providers that have conflicting resource names should include the addition of the provider = attribute.
Actual Behavior
I believe resources with the same type names currently are just overwritten by the last one in. This can also probably be observed in 0.12 with google and google-beta.
The text was updated successfully, but these errors were encountered:
Just realized that provider block completion doesn't work at all with 0.13, since we're looking e.g. for aws, but 0.13 indexes that as registry.terraform.io/hashicorp/aws.
Also provider labels are completed with the FQN too, which is wrong:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the context necessary to investigate further.
ghost
locked and limited conversation to collaborators
Sep 6, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
This affects 0.13 mostly, but to a lesser degree 0.12
Terraform Configuration Files
Expected Behavior
Auto-completion with multiple providers that have conflicting resource names should include the addition of the
provider =
attribute.Actual Behavior
I believe resources with the same type names currently are just overwritten by the last one in. This can also probably be observed in 0.12 with
google
andgoogle-beta
.The text was updated successfully, but these errors were encountered: