One thing I can tell you is that the proximate cause of the panic is that it expects

strings.split(id, "/")[2]

to be a thing - which it is not given the name there.

Is there a more qualified version of the name that might be required?

yeah maybe

a nodepool belongs to a cluster

so maybe i have to qualify it with the clustername

going to try that out…

ok I checked a bit what terraform itself expects as identifier when doing

terraform

import

turns out it expects

<zone>/<cluster_name>/<pool_name>

and when using this in pulumi as second param it actually works.

So I guess the real problem here is that pulumi errors out with some useless error message (whereas terraform gives an actually useful error message). Let me grab the error message that terraform would give when using an incorrect identifier…

ok terraforms error message looks like this when attempting to use simply

default-pool

as identifier:

google_container_node_pool.default_pool: Importing from ID "default-pool"...

Error: google_container_node_pool.default_pool (import id: default-pool): import google_container_node_pool.default_pool (id: default-pool): Invalid container cluster specifier. Expecting {zone}/{cluster}/{name} or {project}/{zone}/{cluster}/{name}

Actually pretty helpful 🙂