This message was deleted.

sparse-intern-71089

11/28/2023, 5:53 AM

This message was deleted.

brave-planet-10645

11/28/2023, 8:34 AM

The gist of this is that by default we write a checkpoint for every resource that gets updated. This means we know exactly what’s going on at the time. With the skip checkpoint env var set to true, we just write once when everything is done so you don’t get the tracking that you would otherwise.

cuddly-magician-97620

11/28/2023, 4:51 PM

Yup, I understand that part. Then what does it mean that self-managed backends "_typically store a singular Pulumi state file._"? Since I'm using S3 bucket backend, then

PULUMI_EXPERIMENTAL=1 PULUMI_SKIP_CHECKPOINTS=true

should not make a difference for me. But it does. Big time. Hours vs. minutes kind of difference. Why?

brave-planet-10645

11/28/2023, 4:53 PM

Because we’re updating that file multiple times (per checkpoint) during the update as opposed to once

cuddly-magician-97620

11/28/2023, 5:17 PM

Then the self-managed backend is written multiple times (per checkpoint), and the statement in the docs "_typically store a singular Pulumi state file._" is misleading, right?

brave-planet-10645

11/28/2023, 8:24 PM

No, we’re writing to the same single file multiple times

cuddly-magician-97620

11/28/2023, 9:47 PM

Ah, OK, that makes sense. Thanks!

2 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.