This message was deleted.

sparse-intern-71089

05/25/2023, 11:52 PM

This message was deleted.

steep-sunset-89396

05/26/2023, 12:34 AM

Hey hey Hey @delightful-jelly-17346 1. if you run

pulumi import ...

that should do it. For each resource type you'd like to import, check the documentation page and at the bottom you will usually fund the correct import syntax. 2. If you want the actual cloud resource name (ie, the physical name), you need to use one of the properties as the result of creating the resource.Look at this example and how

bucket.id

is used to export the actual bucket name.

steep-sunset-89396

05/26/2023, 12:37 AM

On the last point, you can uncover modified resources by running

pulumi preview --refresh

which will retrieve the latest resource state from your cloud env. Then, you should either 1. patch your code to match the modified in the cloud and run the previous command above to ensure there are no changes. And then appy those changes with

pulumi up --refresh

which should also result in no changes. 2. simply run

pulumi up --refresh

to discard changes present in the cloud and use the current source code as the desired state for those resources. Pulumi will then do its best to revert those changes (ie, update the cloud resources)

delightful-jelly-17346

05/26/2023, 12:40 AM

Thanks Aurelien, I will give them a go:)

narrow-wall-86026

05/31/2023, 3:57 AM

Hey Wilson, would it make sense to have a follow-up next week? You can invite the team to join the zoom if you'd like.

6 Views

Open in Slack

Previous Next

Pulumi Community

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.