This message was deleted.

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

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.

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

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

).