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_directory_service_directory" plan causes a panic if the resource is deleted manually #6292

Closed
asvoboda opened this issue Apr 21, 2016 · 2 comments · Fixed by #6294
Closed

Comments

@asvoboda
Copy link

Hi there,

Terraform Version

Terraform version: 0.6.14

Affected Resource(s)

  • aws_directory_service_directory

Terraform Configuration Files

resource "aws_directory_service_directory" "microsoft-ad" {
  name = "${var.ad-fqdn}"
  password = "whatever"
  size = "Small"
  type = "MicrosoftAD"

  vpc_settings {
    vpc_id = "${var.vpc-id}"
    subnet_ids = [ "${element(split(",", var.public-mgmt-subnet-ids), 0)}", "${element(split(",", var.public-mgmt-subnet-ids), 1)}" ]
  }
}

Debug Output

https://gist.github.com/asvoboda/0f1fb8bbc7267aa12d5c59b37f249e6d

Expected Behavior

Terraform continues merrily on its way, just as it does for any resource that was manually deleted.

Actual Behavior

Terraform panics and crashes.

Steps to Reproduce

  1. terraform apply and creates a ds resource
  2. Delete that resource manually and wait until it is fully removed.
  3. terraform plan, and terraform panics
@stack72
Copy link
Contributor

stack72 commented Apr 22, 2016

Hi @asvoboda
thanks for the bug report. I have just submitted a PR that will fix this. It will be released as part of 0.6.15

Paul

@ghost
Copy link

ghost commented Apr 26, 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 26, 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.

2 participants