search

pulumi / deploy-demos

8 stars 5 forks source link

Use a step function for proper TTL delays #37

Open blampe opened 1 year ago

blampe commented 1 year ago

The example was using SQS which doesn't allow delays on a per-stack basis or for a duration longer than 15 minutes.

This uses a step function instead, which can wait up to a year before destroying the stack.

This also invokes the destroy step as a containerized lambda with automation API.

EvanBoyle commented 1 year ago

The example was using SQS which doesn't allow delays on a per-stack basis or for a duration longer than 15 minutes.

I believe that the lambda will fail and then continuously retry the message until the SQS message ages out of the queue - max 4 days by default.

Step functions is substantially cleaner, and a year is much better! Also love that we're using automation API here 🎉

EvanBoyle commented 1 year ago

Darn, I'm just realizing how limiting https://github.com/pulumi/pulumi/issues/11314 is for this example.