https://pulumi.com logo
#general
Title
# general
o

orange-tailor-85423

05/09/2019, 9:08 PM
is this something about the version of the provider that built the particular cluster? Because the code that builds the cluster is identical
w

white-balloon-205

05/09/2019, 9:08 PM
I expect these must be older versions of the
gcp
provider. I know that
location
was added not too long ago.
o

orange-tailor-85423

05/09/2019, 9:09 PM
ok - so those clusters / node pools were stood up with version ‘x’ that didn’t have/support that?
is there a way to tell which version of the provider built the cluster?
{ “urn”: “urnpulumialpha:viserionpulumiprovidersgcp:default”, “custom”: true, “id”: “74bf7ac5-2115-4fc7-a209-e0c5d0064e86”, “type”: “pulumiprovidersgcp”, “inputs”: { “project”: “mindbody-alpha”, “version”: “0.16.6" } },
{ “urn”: “urnpulumistaging:viserionpulumiprovidersgcp:default”, “custom”: true, “id”: “d6015732-4e21-4193-9d4c-08f86b2f5296”, “type”: “pulumiprovidersgcp”, “inputs”: { “project”: “mindbody-staging” } },
{ “urn”: “urnpulumiprod:viserionpulumiprovidersgcp:default”, “custom”: true, “id”: “604817e4-22e8-4153-beb3-38f90e1e6a84”, “type”: “pulumiprovidersgcp”, “inputs”: { “project”: “mindbody-prod” } },
w

white-balloon-205

05/09/2019, 9:45 PM
It shouldn't matter what version originally deployed the resource, what should matter is that the version you are using matches the code changes you are trying to deploy.
o

orange-tailor-85423

05/09/2019, 9:46 PM
ok
so if running same pulumi repo/program…should be non-issue?
w

white-balloon-205

05/09/2019, 9:47 PM
If you are running the same program with the same versions of your dependencies, you should get the same results. The error you are seeing here suggests you are running a newer program with an older version of the provider in one of your environments.
o

orange-tailor-85423

05/09/2019, 9:49 PM
define environment in this case - the place where the pulumi CLI runs?
or something in the GCP env itself