You can do some manual steps to import resources similar to what you described - export your stack file, add the resource with its associated cloud id (you can omit all the properties about it), then import it back into your stack, and do

pulumi refresh

. This will fill in all its properties.

Be sure to get the urn and provider references correct for each resource you’re adding to the stack file. Then you’ll need to get the code to match the resource otherwise pulumi will try to change the resource on the next

pulumi up

.

Please do this first in a test environment so you don’t import and then unintentionally change or destroy any resources. 😬

That’s why I want to know how to import 😄

What I’d really like is a way for pulumi to be run in some sort of “import/refresh” mode where it runs the engine like in “update” but instead of creating resources, it imports them if they match the relevant information (ie, tags, attributes etc). That way, it avoids using the “data source” type functions because there’s no difference, perhaps the opts could have a “import_before_create” option or something.

@gentle-diamond-70147 The fields

"custom": true

&

type

must also be set for the manual import. I.e., you need at least these fields in the stack, right?: •

urn

, •

custom

, •

id

, •

type

, •

parent

, •

provider

@stocky-island-3676 generally any of the functions listed in the API documentation are data sources - e.g. https://pulumi.io/reference/pkg/nodejs/@pulumi/aws/index.html#getAvailabilityZones

And yes, you need to set all of those. Sorry I omitted some of them in my answer.