This message was deleted.

sparse-intern-71089

07/07/2023, 2:22 AM

This message was deleted.

little-cartoon-10569

07/07/2023, 2:30 AM

That's an AWS question, rather than a Pulumi-specific question. The snapshot identifier corresponds to the same field in the RDS console or the APIs. It is used when creating or restoring a snapshot, as opposed to when deploying via Pulumi. Any time you trigger either of those actions, that field is used by RDS, not Pulumi.

little-cartoon-10569

07/07/2023, 2:30 AM

If you update that field via Pulumi, nothing special will happen in RDS, other than the field will be blanked. However, you won't be able to create or restore a snapshot until you put a value in there.

little-cartoon-10569

07/07/2023, 2:31 AM

Generally, you should not change the value of that field once an instance is created. RDS looks after versioning; if you create 10 snapshots, they don't overwrite each other: the identifier is used as a prefix.

little-cartoon-10569

07/07/2023, 2:32 AM

If you do change the value of the field, then existing snapshots (with the old identifier) can't be restored into the instance (until you change it back).

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.