Skip to content
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

Possible undocumented bug-fix/regression in 1.2.0 when using depends_on and modules with provider blocks #31114

Closed
chrislwade opened this issue May 23, 2022 · 3 comments
Labels
bug duplicate issue closed because another issue already tracks this problem

Comments

@chrislwade
Copy link

Terraform Version

Terraform v1.1.9
on darwin_amd64

Your version of Terraform is out of date! The latest version
is 1.2.0. You can update by downloading from https://www.terraform.io/downloads.html

and

Terraform v1.2.0
on darwin_amd64

Terraform Configuration Files

See https://github.com/chrislwade/terraform-depends-on-module-with-provider.

Expected Behavior

Either this example should continue to work (init, validate, and plan), or the release notes for 1.2.0 should be updated to reflect the fact that this scenario was fixed and not intended to work.

Actual Behavior

Template fails init after updating to Terraform 1.2.0.

Steps to Reproduce

  1. Use Terraform version 1.1.9.
  2. terraform init
  3. terraform validate
  4. Confirm template inits and validates.
  5. Use Terraform version 1.2.0.
  6. terraform init
  7. Confirm template fails init.

References

@chrislwade chrislwade added bug new new issue not yet triaged labels May 23, 2022
@crw
Copy link
Collaborator

crw commented May 23, 2022

Thanks for the report!

@crw
Copy link
Collaborator

crw commented May 23, 2022

Duplicate of #31081 -- fix will be released in 1.2.1.

@crw crw closed this as completed May 23, 2022
@crw crw added duplicate issue closed because another issue already tracks this problem and removed new new issue not yet triaged labels May 23, 2022
@github-actions
Copy link

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 details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug duplicate issue closed because another issue already tracks this problem
Projects
None yet
Development

No branches or pull requests

2 participants