This message was deleted.
# general
s
This message was deleted.
b
Could try automation? define one stack, then use that as an overlay/default for others.
i.e. maintain 12 stacks but have them all be executed from one place with one config (possibly in paralell depending on how things work out)
e
I like the idea of the overlay, but I’m wondering how to handle encrypting secrets. If the default production stack has secrets, it wouldn’t work with the overlay because the secrets will have a different
encryptedkey
. Am I understanding this correctly?
b
well, that's true.
though, technically, with automation you could handle your secrets manually.
i.e. directly interface with vault or keyvault or whatever it might be during your exectution
👍 1
e
I ended up using this package to merge yaml files. https://github.com/miracl/conflate
Copy code
filename := "Pulumi.esus-k8s-play-5-a.yaml"

c, err := conflate.FromFiles(filename, "Pulumi.play.yaml")

overlay, err := c.MarshalYAML()

ioutil.WriteFile(filename, overlay, 0644)
I’m using the same
encryptkey
for both stacks, so the overlay doesn’t affect the secrets.
And that happens before pulumi
run()
b
that's awesome 😄