clever-byte-2155112/15/2020, 7:21 AM
to a more up-to-date version. But my stack wasn’t able to refresh if I didn’t have the old plugin version existing on the machine (I’m running in container so I only have the recent plugin version) Other pulumi provider have this behaviour and I was wondering if this is a bug
(I was upgrading from 2.6.1 to 2.6.3)
Diagnostics: pulumi:providers:kubernetes (default_2_6_1): error: no resource plugin 'kubernetes-v2.6.1' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource kubernetes v2.6.1`
gentle-diamond-7014712/15/2020, 2:55 PM
will use the last used plugin version until an
occurs with a newer plugin version.
clever-byte-2155112/15/2020, 3:26 PM
is the only plugin so far that behaves this way. I’m using azure-nextgen, gcp, aws, tls and random and none of them behaves this way.
gentle-diamond-7014701/26/2021, 2:55 PM