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
Terraform v0.11.x changes the provider and module relationships significantly. This causes issues with Teraform provider version constraints which allowed modules to specify minimum versions of providers that are required. Typhoon uses these constraints to ensure end-users have appropriate plugin versions.
Re-run terraform plan and terraform apply on your infrastructure. Plan should claim there are 0 changes, but run apply anyway.
Now you should be able to use Terraform again normally.
If you run plan, you won't see random prompts for provider fields you're setting
If you comment or delete a module instance and terraform apply, the cluster is correctly deleted
Yes this is silly.
Long term
Upstream is aware of the impact on modules that use provider versions. They're hoping to address with hashicorp/terraform#16835 in a future v0.11.x release. We may wait on this instead of asking dear users to hop through the hoops above. Feel free to weigh in on how you'd like to see this proceed.
The text was updated successfully, but these errors were encountered:
Bug
Environment
Problem
Terraform v0.11.x changes the provider and module relationships significantly. This causes issues with Teraform provider version constraints which allowed modules to specify minimum versions of providers that are required. Typhoon uses these constraints to ensure end-users have appropriate plugin versions.
You can find the full saga in hashicorp/terraform#16824.
Short term
Stick with Terraform v0.10.x.
Mid term
I'm working on docs to show how v0.11.x can be used. Basically,
Explicitly add every provider in
providers.tf
and give it an alias, such as "default".Edit each instance of a module in your infrastructure to explicitly pass the providers.
Re-run
terraform plan
andterraform apply
on your infrastructure. Plan should claim there are 0 changes, but run apply anyway.Now you should be able to use Terraform again normally.
terraform apply
, the cluster is correctly deletedYes this is silly.
Long term
Upstream is aware of the impact on modules that use provider versions. They're hoping to address with hashicorp/terraform#16835 in a future v0.11.x release. We may wait on this instead of asking dear users to hop through the hoops above. Feel free to weigh in on how you'd like to see this proceed.
The text was updated successfully, but these errors were encountered: