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
➜ ttest git:(master) ✗ terraform destroy
digitalocean_floating_ip.kubernetes_ip: Refreshing state... (ID: 174.138.114.123)
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
- destroy
Terraform will perform the following actions:
- module.kubernetes.digitalocean_floating_ip.kubernetes_ip
Plan: 0 to add, 0 to change, 1 to destroy.
Do you really want to destroy?
Terraform will destroy all your managed infrastructure, as shown above.
There is no undo. Only 'yes' will be accepted to confirm.
Enter a value: yes
module.kubernetes.digitalocean_floating_ip.kubernetes_ip: Destroying... (ID: 174.138.114.123)
module.kubernetes.digitalocean_floating_ip.kubernetes_ip: Destruction complete after 0s
Error: Error applying plan:
1 error(s) occurred:
* module.kubernetes.output.kubeconfig: Resource 'data.external.kubeconfig' does not have attribute 'result' for variable 'data.external.kubeconfig.result'
Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
➜ ttest git:(master) ✗
The text was updated successfully, but these errors were encountered:
Hi @justinbarrick -
Sorry for the long silence on this, and I'm sorry you've run across this bug. It's a known issue; the main (current) conversation is in #18026 so I am going to close this ticket in favor of that one. Please go ahead and add your 👍 to that issue.
Thanks!
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
locked and limited conversation to collaborators
Apr 2, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am using the following terraform module called
test/test.tf
:And then I have
test.tf
:Run:
It will fail on
terraform destroy
:The text was updated successfully, but these errors were encountered: