This message was deleted.

What I don't want is to have to do this all the time:

https://www.pulumi.com/docs/concepts/options/version/

This is not a Pulumi operation. You will need to use the functionality provided by your language or another library to do this.

Any suggestions/examples on how to do that?

The most simple and self-documenting would be to use a Pulumi config setting and require the system or developer to change it. This allows for external tools to do the work, to get the value from your CI vaults, or any other place. Alternatively, you could write a value to well-known global location (a vault, DynamoDB table, even a file in an S3 bucket), then read-increment-write it. This has a problem in that there is limited user control, and is susceptible to being broken by (for example) failed deployments, credential expiry, accidental change / deletion, and more.

Yep that all makes sense. I am just a solo dev right now, so was tired of copy and pasting some randomly generate string for the latest image to my other application that needs to know what to pull

Is a timestamp suitable?

Hmmm thats better? Still more or less the exact same problem, but an easier to interpret string

Or maybe the sha1 of the latest commit?

eb1e1cbc3296736335a6f36b694a182d5319b63fefc0481de768c1cb67a23b6c

->

1693929292010

If you use a tool that supports it (npm/yarn, maven with the version extension, etc.) you can use your project's package version.

Ya that's not a terrible idea

Maybe this is kinda over-engineering, but why not using a Dynamic Provider which keeps the version under control and has one or more keepers that will cause the version to bump if the keeper change. So if the git commit is a keeper, the version will bump if the commit changes. Another advantage the version could then be an Pulumi output that could be referenced in other Pulumi programs.