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
When executing terraform import, the other, non-tagged node pool is imported.
digitalocean_kubernetes_cluster.doks_hosted_cluster: Importing from ID "80654840-..."...
digitalocean_kubernetes_cluster.doks_hosted_cluster: Import prepared!
Prepared digitalocean_kubernetes_cluster for import
Prepared digitalocean_kubernetes_node_pool for import
digitalocean_kubernetes_node_pool.doks_hosted_cluster: Refreshing state... [id=152b6618-...]
digitalocean_kubernetes_cluster.doks_hosted_cluster: Refreshing state... [id=80654840-...]
Import successful!
The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.
Steps to Reproduce
See "Actual Behavior". Terraform Configuration Files main.tf:
Bug Report
Describe the bug
When importing an existing Kubernetes cluster using
terraform import digitalocean_kubernetes_cluster
, the incorrect node pool ID is imported.Affected Resource(s)
Expected Behavior
With the following configuration:
I expect node pool
6f41bd3b-...
, tagged asterraform:default-node-pool
to be imported when executingActual Behavior
When executing
terraform import
, the other, non-tagged node pool is imported.Steps to Reproduce
See "Actual Behavior".
Terraform Configuration Files
main.tf
:Expected behavior
The node pool tagged as
terraform:default-node-pool
should be imported when executingterraform import digitalocean_kubernetes_cluster
.Debug Output
I'm concerned about the level of detail in the debug output; I have the gist and can email the link if necessary.
Panic Output
None
Additional context
Changing the
terraform:default-node-pool
tag to the secondary node pool results in the "correct" node pool being imported along with the cluster.Important Factoids
None
References
None
The text was updated successfully, but these errors were encountered: