Allow the TTL on the updates.auto.pulumi.com objects to be changed

[pierskarsenbarg]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

When an update has taken place, the updates.auto.pulumi.com object remains. If there are a lot of updates then there are a lot of these objects.

There is a TtlAfterCompleted field that if you set by editing the object YAML, you can shorten but the default for this is 24 hours and there doesn't seem to be a way of setting that in advance.

Affected area/feature

[EronWright]

My proposal for this is to expose an updateTemplate field in the Stack spec, so that you could customize this field (and possibly others in the future). WDYT?

Does anyone feel that the default value of 24 hours is too long (or not long enough)?

[pierskarsenbarg]

The comment from the user I was talking to was that they use ArgoCD and because all the objects are displayed it made it difficult to read (and slow) because there were so many.

What's the purpose of the update object? Is it so people can go back and view previous updates?