This message was deleted.

sparse-intern-71089

07/14/2021, 10:06 AM

This message was deleted.

tall-librarian-49374

07/14/2021, 11:04 AM

That’s because you create your Connection resource inside an

Apply

which doesn’t run in the original preview (there’s no value to apply yet)

tall-librarian-49374

07/14/2021, 11:06 AM

You should be able to refactor your code to avoid creating resources within an

Apply

. Instead, create it always, but pass args that are calculates with `Apply`s

tall-librarian-49374

07/14/2021, 11:06 AM

Also, you wouldn’t need

dependsOn

in this case. Not sure you can do

Parent

though.

mysterious-australia-14256

07/14/2021, 11:12 AM

Thanks @tall-librarian-49374, I'll give it a go. Is there a way to get the destroy to remove the created object rather than the deployment?

tall-librarian-49374

07/14/2021, 11:24 AM

No, I’m afraid

tall-librarian-49374

07/14/2021, 11:24 AM

Deployment is a black box for us

mysterious-australia-14256

07/14/2021, 11:25 AM

ok thanks

mysterious-australia-14256

07/14/2021, 11:48 AM

@tall-librarian-49374 given that I can get the ID of the created resource via the OutputResources returned by the deployment, is there any way I can then import the object so Pulumi then knows about it and can delete it? I'm guessing not as I think you have to specify all of the settings when doing an import and the reason I'm using an ARM deployment in the first place is that some properties aren't supported by the Pulumi code.

tall-librarian-49374

07/14/2021, 11:52 AM

Yes, I think you are correct that you can’t import a resource if you can’t define it.

👍 1

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.