This message was deleted.
# generals
sparse-intern-71089
04/27/2021, 7:24 PMThis message was deleted.
l
little-cartoon-10569
04/27/2021, 7:37 PMThat sounds like what Pulumi does. Changes are applied by Pulumi only when the code (new value) and the state (previous value) differ. Do you have additional requirements beyond this?
f
fast-dinner-32080
04/27/2021, 8:46 PMHere is my use case.
1. do a lookup to see what the property value should be set to for all new resources
2. create resource if it needs to be created with that properties value
Next run:
1. do a lookup to see what the property value should be set to for all new resources
2. do not change that property value on existing resources
3. create new resources with the new property value that is not the same as when older ones were created
fast-dinner-32080
04/27/2021, 8:48 PMThe main issue is pulumi wants to set that property on old and new ones to a new value than what it used to be set too.
fast-dinner-32080
04/27/2021, 8:48 PMthis property is managed outside pulumi except for on initial creation.
l
little-cartoon-10569
04/27/2021, 8:58 PMThere's likely dozens of ways to achieve this, but the essence is: take advantage of the fact that you're using a normal programming language.
little-cartoon-10569
04/27/2021, 8:58 PMFor me, I'd probably use automation-api and set the stack config with a value when creating the stack, and never change it again.
little-cartoon-10569
04/27/2021, 8:59 PMThough a simple ba(s|tc)h script would achieve the same thing very concisely.
little-cartoon-10569
04/27/2021, 9:01 PMUsing the stack config has the advantage that you can easily see in source control which value was used to create the resources, since it's in your Pulumi.<stack>.yaml.
f
fast-dinner-32080
04/27/2021, 9:02 PMWe are already using external lookups and a bunch of logic in the app that is outside of core Pulumi. The issue is our component contains the resource to create which looks up the current default from an outside source. This value is always changing and we need new resources using the component to use the current default. If I run it again after this default changes it looks up a new value and shows all existing ones should change too.
fast-dinner-32080
04/27/2021, 9:03 PMTrying to figure out a way so it doesn’t change that property at all or think it needs to after it is created but any net new ones should use the default
l
little-cartoon-10569
04/27/2021, 9:03 PMI suggest moving the look-up-and-set logic to a little earlier in the workflow. Move it to stack creation time, instead of resource creation time.
little-cartoon-10569
04/27/2021, 9:04 PM(Assuming that you create all your resources at the same time as you initially up your stack..)
g
glamorous-helmet-50600
04/27/2021, 9:30 PMI have a similar challenge actually. In my case is probably simpler to get around: I'm checking if a certificate exists and if not then I create the resource, so the declaration of the resource is within a condition. The problem: on the second+ pulumi run the condition isn't met (because the certificate has been created) so the code to declare the certificate isn't run and pulumi treats it as a delete of the certificate (and rightfully so).
l
little-cartoon-10569
04/27/2021, 9:32 PMFor that case, importing the certificate to Pulumi is probably the most idiomatic solution, I think?
little-cartoon-10569
04/27/2021, 9:33 PMAgain, assuming that it happens only once (when creating the stack)...
g
glamorous-helmet-50600
04/27/2021, 9:41 PMNot entirely sure what you mean by importing the certificate to Pulumi (still a newbie in Pulumi). I'm currently creating it on the fly as part of the pulumi run (and then I use the pfx to create the certificate resource in azure)
l
little-cartoon-10569
04/27/2021, 9:47 PMIf you're not creating the certificate outside of Pulumi, and it is only ever created by Pulumi code, why do you need to check if it exists?
little-cartoon-10569
04/27/2021, 9:47 PMThat's Pulumi's job.
g
glamorous-helmet-50600
04/27/2021, 9:54 PMIndeed, I wrongly assumed I wouldn't be able to retrieve the pfxblob of an existing certificate resource but looking at the "GetCertificateResult" I see it includes all properties I need. I have needlessly over-complicated this lol thanks for the hint, it's very clear now what I need to do 👍
👍 1