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

From my own experience you'll have to first import it exactly as it is.. *Then* you can change the content in your resource definition, and remove the import option.

Unfortunately that means you need multiple runs and manual intervention. I'm dealing with multiple AWS accounts and this would be very inconvenient.

Hmm, can you look up the original value for each account first? I'm assuming you loop over the accounts?

Is there a way to get a list of resources? Then it would be a matter of if exists then import else modify

Maybe <https://www.pulumi.com/docs/reference/pkg/aws/ssm/getdocument|https://www.pulumi.com/docs/reference/pkg/aws/ssm/getdocument>

Yes, but with just that I don't know if I have to import or modify

Can't you use it to import first, from all accounts? Then when you're done with the importing, you can run again with a content update instead of the lookup.

Yes, that's my idea. I would have to run it twice to get the desired result, but it's still better than now.  But I don't want to have to run a separate piece of code for that.

It's just that I don't know to differentiate between the import run from the modify run

Can you clarify what you mean by "import first"?

If there was a way to get the resource list from the stack, then I could know, but there doesn't seem to be a way to do so