This message was deleted.

sparse-intern-71089

08/10/2022, 9:57 AM

This message was deleted.

echoing-dinner-19531

08/10/2022, 10:15 AM

I think it should, ignore_changes just tells it to use the values it last saw for inputs. The replace should still happen though.

fierce-ability-58936

08/10/2022, 8:12 PM

I think it shouldn't. More specifically, I had ignore_changes for one attribute so it didn't recreate the resource automatically, but then I ran

up --replace

to actually replace it and expected it to create a new resource based on the new definition in the code.

echoing-dinner-19531

08/10/2022, 10:31 PM

ah right, you kinda need an ignore-ignore-changes option 😬 If any other (non-ignored) attribute had changed and triggered a replace the "ignore_changes" properties would still have their old value, doesn't seem consistent for

--replace

to change from that. Might be worth opening an issue on github about this

fierce-ability-58936

08/11/2022, 10:12 PM

Actually when testing the above on a simple yaml project it behaves exactly as I expect. So maybe my prior experience was limited by either the language (Python) or provider (Azure native), or even a specific resource (https://www.pulumi.com/registry/packages/azure-native/api-docs/dbforpostgresql/server/) or even a specific input (

geoRedundantBackup

fierce-ability-58936

08/11/2022, 10:12 PM

I'll have another go to replicate the exact environment, but otherwise it looks good.

5 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.