No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

If you don’t change the order, does a `pulumi up` work without asking to replace?

ha, that's what I realized just now. it doesn't :slightly_smiling_face:

thanks. now I need to decipher what the pending changes are. in tf I only have a single property being the name

aha. it all works as expected. I had to remove the `import:` statements so not to trigger re-import

yeah, so i think you’re likely running into <https://github.com/pulumi/pulumi/issues/3657>

in principle, you should be able to keep the `import` there

but per the issue:
&gt; The resources that trigger this are ones that use a different format of identifier for the `import` input than they do for the `id` property. The vast majority of resources allow passing in the identifier used in the `id` property as the input to an `import` - but there are a few that do not.
which i think is the case for the resource you’re importing

yep. thanks. I can add the `id` next to the import and it becomes a noop, but then I suppose I can't create the resources in the same code block so I'll still have to manage several for the migration

either way, I have a way to proceed. thanks!