jolly-window-25842
11/14/2023, 12:05 PMpulumi refresh
and then pulumi up
to recreate it. The refresh
detected a couple of small changes and so I confirmed it. Now, if I run pulumi up
it fails because it wants to re-create all Cloud SQL database instances (which are protected), however the refresh
didn't detect any changes to the dbs. What are my option? Right now, the pulumi state is completely messed up.dry-keyboard-94795
11/14/2023, 12:07 PMpulumi preview --diff
to identify the changes pulumi thinks needs making to the dbsjolly-window-25842
11/14/2023, 12:11 PMunable to replace resource "urn:......." as it is currently marked for protection
dry-keyboard-94795
11/14/2023, 12:12 PMjolly-window-25842
11/14/2023, 12:17 PMrefresh
show me these changes? like there is a bucket that now shows lifecycleRules
were deleted, but refresh
didn't show itdry-keyboard-94795
11/14/2023, 12:18 PMjolly-window-25842
11/14/2023, 12:22 PMdry-keyboard-94795
11/14/2023, 12:24 PMjolly-window-25842
11/14/2023, 12:26 PMdry-keyboard-94795
11/14/2023, 12:48 PMjolly-window-25842
11/14/2023, 1:05 PMstale-answer-34162
11/14/2023, 1:27 PMjolly-window-25842
11/14/2023, 2:50 PMrefresh
. And finally, GCP autoscales db disk size and since it was higher than what was set in the pulumi code, pulumi wanted to replace them.
I still think the refresh
command was off: it didn't show any of these things in the preview.
Thanks for your help @dry-keyboard-94795, I really appreciate it!stale-answer-34162
11/14/2023, 2:51 PMdry-keyboard-94795
11/14/2023, 3:06 PMignoreChanges
option so the auto-sizing doesn't cause the same issue in future.
The defaults in GCP, I believe they're not supposed to show in the refresh output, but they're also not supposed to show in the diff either.
Does it still show changes to apply to the db?