rich-exabyte-94739
11/13/2020, 4:29 AMrds.Instance
and pulumi up
, everything works as expected. However - when we run pulumi up
again to make other changes Pulumi tries to replace the database entirely, using the snapshot ID previously provided.
We've tried modifying the rds.Instance
, removing the snapshot ID in subsequent pulumi up
commands but the same issue still persists. What are we doing wrong? How do we get Pulumi back to a good state where it's not trying to constantly try and replace our DB with the snapshot?clever-byte-21551
11/13/2020, 4:32 PMrich-exabyte-94739
11/13/2020, 9:58 PM