https://pulumi.com logo
#general
Title
# general
n

nice-rain-32013

07/03/2023, 9:06 AM
Strange thing today, even though
preview
tells me there is no change on the stack,
up
wants to tear down and rebuild an RDS Postgres instance; any clues on what to look at to figure out a reason?
Copy code
pulumi:pulumi:Stack: (same)
    [urn=urn:pulumi:dev::*****-rds::pulumi:pulumi:Stack::*****-rds-dev]
    > pulumi:pulumi:StackReference: (read)
        [id=*****/*****/dev]
        [urn=urn:pulumi:dev::*****-rds::pulumi:pulumi:StackReference::*****/*****/dev]
        name: "*****/*****/dev"
    +-aws:rds/instance:Instance: (replace) 🔓
        [id=*****-devID1]
        [urn=urn:pulumi:dev::*****-rds::aws:rds/instance:Instance::*****-dev]
        [provider=urn:pulumi:dev::*****-rds::pulumi:providers:aws::default_5_41_0::9630e6c1-0ca7-4491-9da6-64f8c5471761]
      ~ identifier: "*****rds-devID1" => "*****-rds-dev-ID2"
Resources:
    +-1 to replace
    3 unchanged
l

little-cartoon-10569

07/03/2023, 9:34 AM
I'd lay odds on it being a false positive. You could try manually turning on the RDS protected flag on that instance (not the Pulumi on, but using the console to turn on the AWS protection), then run the
up
knowing that if Pulumi does try to delete it, AWS will prevent the deletion. Then you'll know if Pulumi really will delete it.
I don't know why it happens, but it does. Anecdotally, it happens more frequently on stacks that are updated only very rarely.
n

nice-rain-32013

07/03/2023, 9:59 AM
thanks a LOT @little-cartoon-10569, very useful!
2 Views