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

AWS provider configuration not available in delete module #1447

Closed
johnrengelman opened this issue Apr 9, 2015 · 7 comments · Fixed by #1452
Closed

AWS provider configuration not available in delete module #1447

johnrengelman opened this issue Apr 9, 2015 · 7 comments · Fixed by #1452

Comments

@johnrengelman
Copy link
Contributor

Simliar to #1380 (comment)

Steps

  • Create a main.tf that declares and configures the aws provider.
  • Add a module (declares only aws resources, not the provider)
  • terraform apply - everything is created
  • Remove the module from main.tf
  • Run terraform plan

Result:

 $GOPATH/bin/terraform plan
There are warnings and/or errors related to your configuration. Please
fix these before continuing.

Errors:

  * provider.aws: "region": required field is not set

Tested using the following:

$GOPATH/bin/terraform --version
Terraform v0.4.1-dev (c0196d948d942a32a46fb9ef203076d3be134e4d)
@mitchellh
Copy link
Contributor

Should be fixed!

@jaygorrell
Copy link

Is there already an open version of this bug? It seems to be happening again, if it was ever fixed.

@apeeters
Copy link

apeeters commented Aug 5, 2016

The bug seems to resurface in TF 0.7.

@hazim1093
Copy link

as @apeeters pointed out, we're facing the same bug again after upgrade to TF 0.7.
We're using nested modules and while destroying them, terraform asks to enter value for region

@pmoust
Copy link
Contributor

pmoust commented Sep 20, 2016

Experiencing the same in TF v0.7.3

@mewm
Copy link

mewm commented Sep 20, 2016

I experienced this suddenly today. I'm not sure exactly what did it, but after nuking .terraform folder and running terraform get my plan could execute

@ghost
Copy link

ghost commented Apr 22, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants