I've just come across a Pulumi stack maintenance script, and thought.. this belongs in https://github.com/pulumiverse. But not in its own repo, it's too small! (It just exports a stack, loads it as a JSON object, removes the pending_operations element and re-imports it.) What model(s) would be suitable for maintaining a repo of very small contributions like this?

Note that

pulumi refresh

does most of that operation today. It just leaves pending creates, and we're going to make it remove those as well at some point soon.

It removes pending updates and deletes but leaves pending creates?

Currently, we've internally agreed it should remove pending creates as well so we'll get round to making that change soon. Been a bit pre-occupied getting yaml and java and everything else ready for PulumiUP for the last few weeks though 🙂

Just to confirm: does it currently remove pending updates and deletes?

yes

Just spoke to client using the script, they're looking forward to that update! 👍

How about we create a mono-repo called

pulumi-utils

?

Yes some day.. don't need it just now, since this particular script has been rendered pointless due to

pulumi refresh

:)