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

Provider fails to destroy consul_keys. #35

Closed
sakaru opened this issue Jan 11, 2018 · 2 comments
Closed

Provider fails to destroy consul_keys. #35

sakaru opened this issue Jan 11, 2018 · 2 comments

Comments

@sakaru
Copy link

sakaru commented Jan 11, 2018

Terraform Version

$ terraform -v
Terraform v0.11.2
+ provider.consul v1.0.0

Affected Resource(s)

Please list the resources as a list, for example:

  • consul_keys

Terraform Configuration Files

provider "consul" {
  address = "localhost:8500"
  datacenter = "dc1"
}
resource "consul_keys" "test" {
  key {
    path = "foo"
    value = "bar"
  }
}

During the second run it is:

provider "consul" {
  address = "localhost:8500"
  datacenter = "dc1"
}

Debug Output

https://gist.github.com/sakaru/e68c9918674bba98428f79ae56ae272d

Panic Output

n/a

Expected Behavior

The consul_keys.test resource should be destroyed from the consul service.

Actual Behavior

The resource is not destroyed. Despite what the output says.

Steps to Reproduce

  1. terraform apply
  2. Remove consul_keys.test resource from the main.tf file
  3. Re-run terraform apply (and approve)

Important Factoids

$ consul version
Consul v1.0.2

References

None

@sakaru
Copy link
Author

sakaru commented Jan 11, 2018

Never mind, I didn't see the delete argument reference. Closing issue.

@sakaru sakaru closed this as completed Jan 11, 2018
@btyler97
Copy link

Can I ask why an argument is necessary? If I'm running a destroy, I expect all of the resources to be destroyed. I don't understand why you explicitly have to flag them as "delete." Even the plan and destroy output indicate that the resource is going to be and was destroyed respectively.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants