This message was deleted.

(This is for a Python-GCP project) I am importing a

gcp.container.Cluster

resource by specifying the

import_

option, and I can leave off the majority of the options and still have the preview portion of

pulumi up

succeed with no warning. I can see in the

details

of the preview that the unspecified fields are properly being pulled in from the imported resource (e.g, the nodepools on the cluster). Three specific questions: 1. If I go through with

pulumi up

, can I guarantee that it will not modify any of the existing resources as long as

import_

is in place? 2. If I then remove the

import_

option with those unspecified options unchanged, would it then modify the resources and (e.g.) delete the nodepools that are present on the cluster? 3. After the initial

pulumi up

has been run to import the resource, do I have to remove the

import_

command? a. We are swapping from manually-managed to pulumi-managed infrastructure gradually, so allowing the two to coexist might be nice, especially if the answer to 2. is ‘yes’

Did you not get errors? The docs (just below where you linked) say you should get an error if your code doesn't match the imported resource's in-provider configuration.

You can also use the

pulumi import

CLI command, which might be easier than trying to do it via code. It's what I usually do. Pulumi imports just change the state file, not the resources themselves.

Does anyone use the

pulumi import

command to generate Pulumi code as mentioned in docs? It seems like a good option - how well does it work?

I use the CLI version from time to time. No issues there, if I remember to reference the provider correctly. Usually it's not needed, but in my case it's needed.

Generally, the correct thing to do is to update your code to match the actual configuration (which is why there are warnings and errors, as documented), import, then remove the import option.

I did not get any warnings on the preview, which is at the heart of my question. I’m hesitant to go through with the

up

operation, because I am not confident it will run without modifying the state on the server — especially because removing (most) fields does not affect whether an warning is raised.