https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
k
Personally, I never use the latest tag, rather, i use a specific version and then update that (in config) That way, I can be sure that I'm using the same tested version each time NOTE: This workflow is a work-in-progress, not in production yet :)
s
no i get it, i was thinking the same thing. use a specific tag as a config variable to then run 
pulumi up -y
latest
is bad practice.
i was just hoping there was a feature i had missed to "refresh" deployments
a
There are use-cases where I think using a 
latest
is ok. As an example, I have a report that is a static set of files, build as part of an nginx container image. I can simply trigger a rolling update and get 
latest
image. Here is an SO article that gives a whole bunch of options, including patching the contain image name with a new buildId-based tag. https://stackoverflow.com/questions/40366192/kubernetes-how-to-make-deployment-to-update-image
This is certainly easy.
Copy code
kubectl rollout restart deployment/demo
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by