This message was deleted Pulumi Community #general

Join Slack

This message was deleted.

# general

sparse-intern-71089

10/30/2019, 12:57 AM

This message was deleted.

creamy-potato-29402

10/30/2019, 1:11 AM

You can generally “adopt” resources: https://www.pulumi.com/blog/adopting-existing-cloud-resources-into-pulumi/

creamy-potato-29402

10/30/2019, 1:11 AM

examples are aws but you get the idea

rich-lamp-32782

10/30/2019, 1:13 AM

I was just looking at approaching it this way, thanks!

rich-lamp-32782

10/30/2019, 1:48 AM

So I’ve worked through the import steps, but is there a way I can do this idempotently? It seems that to import the existing resource will require one run, and then appending to it will require running

pulumi up

with different code. If the stack gets recreated from scratch I’d like to be able to adopt and then add to the resource in one run.

rich-lamp-32782

10/30/2019, 1:55 AM

I think I’m having this particular problem due to trying to mainpulate

data

in the configmap which is readonly and the documentation says can’t be updated after creation

white-balloon-205

10/30/2019, 3:05 AM

Re: adopt first and then edit - one approach is to have a config setting that determines this, and run initial deployment with that set to true and then update to false after, and conditionally add the

import; id

only when this is false. (Or something along those lines) Definitely thinking about options to support a more first class version of this workflow. Do also note that adopting the resource may be a little heavy-weight - for example, it would mean that if you later destroy your stack, you will remove the config map. Which is probably not what you want. You may therefore also want to

protect: true

the resource. The broader idea of editing an existing resource in an idea potent way but without taking full ownership is something we’re definitely thinking about as a general thing.

rich-lamp-32782

10/30/2019, 4:38 AM

Thank you for your input Luke! I think for this use case I might work around the problem another way, since I actually do want this configuration to be able to come and go with the stack. Being able to append to the config without taking ownership of it would be the easiest thing here, so glad to hear that’s on your radar as well 🙂

Open in Slack

Previous Next