https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
c
yes.
o
is there a way to do this automatically in the CI system?
c
you want stuff related to an update processed with the previous version of the plugin, to be processed with that version of the plugin.
o
hm
Will I be able to remove 
pulumi plugin install resource kubernetes v0.22.0
from my CI job after this goes up to production then, because the stack will now use 0.23.1?
c
when your last update uses that version, yes.
o
ok
It would be a wonderful feature if like with 
pulumi refresh/up/destroy
we could install missing provider plugins! 🙂 Then we would not need to do a two-step deployment to bump versions, modifying our CI script and package.json, then reverting the change to the CI script in a second deployment
w
It would be a wonderful feature if like with 
pulumi refresh/up/destroy
we could install missing provider plugins!
Yes - we are moving the direction of automatically faulting in plugins if needed. Which command did you run here? And which 
pulumi
version are you running? I thought we had actually already made changes recently to start doing this for 
updates
.
o
Maybe it's because I did an 
up --refresh
?
Copy code
pulumi --non-interactive up --refresh --config-file "${CONFIG_FILE}" --stack "$STACK"
w
Ahh - that could well be - I think we do not do this auto-discovery on 
refresh
yet. I've opened https://github.com/pulumi/pulumi/issues/2799 to look into this.
o
I like that plugins are faulted in like memory pages 😂
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