Hi fellow

pulumi

experts and practitioners, as we implemented our

pulumi

automation without interacting with

pulumi CLI

, we have encountered the following challenges. If there is any common interests in the community of going over these obstacles, we will highly appreciate anyone could share your experience about the following: • How do we import existing resources (not created by

pulumi

) into an established

pulumi

stack? • How do we get the physical name out of a resource instance, and use it in another resource? The name of a resource instance is a

pulumi.output.Output

in Python, which disallows us to use it in subsequent concatenation of building our resource naming convention. • If some

pulumi

managed resources get removed/modified by someone without going through our pulumi program, how should we manage such situations and keep them in sync? Many thanks. @narrow-wall-86026 @steep-sunset-89396

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.

Thanks Aurelien, I will give them a go:)

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.