Is there some metadata mechanism in Pulumi? Like l...
# getting-started
s
Is there some metadata mechanism in Pulumi? Like labels/tags - but something that will not be included in diff? I have the case that I would like to know from which version of mine automation and custom library UP was executed. Right now I am using Azure Tags - but that produce diff, even if nothing else change. (and make a huge noice in diff printout). Simply I would like to just add some metadata into the backend, without including it into a diff.
f
I don’t have a good answer to your question, but you could minimize it by attaching the metadata as properties to a single custom resource. There is metadata attached with each stack update about git commit and pulumi versions, but I don’t know how to add to it.
s
Yes, it seems like a perfect place (pulumi stack history)
Would be nice to be able add a custom properties to it
f
Taking a quick look at the code, you might be able to steal some of the CI variables, but I think it would be better to request a change to allow us to add custom fields
s
which one? Can you point to them?
f
What CI system do you use? The code is run here: https://github.com/pulumi/pulumi/blob/master/pkg/cmd/pulumi/util.go#L932
If you click on line 941, on DetectVars you’ll see there are different implementations that each have different environment variables that it’ll pick up
s
I see, thanks!
l
Would stack tags help? You could write stack tags each time you
up
a stack.