This message was deleted.
# generals
sparse-intern-71089
05/09/2019, 9:08 PMThis message was deleted.
w
white-balloon-205
05/09/2019, 9:08 PM
I expect these must be older versions of the
gcplocationo
orange-tailor-85423
05/09/2019, 9:09 PMok - so those clusters / node pools were stood up with version ‘x’ that didn’t have/support that?
orange-tailor-85423
05/09/2019, 9:35 PMis there a way to tell which version of the provider built the cluster?
orange-tailor-85423
05/09/2019, 9:41 PM{
“urn”: “urnpulumialpha:viserionpulumiprovidersgcp:default”,
“custom”: true,
“id”: “74bf7ac5-2115-4fc7-a209-e0c5d0064e86”,
“type”: “pulumiprovidersgcp”,
“inputs”: {
“project”: “mindbody-alpha”,
“version”: “0.16.6"
}
},
orange-tailor-85423
05/09/2019, 9:43 PM{
“urn”: “urnpulumistaging:viserionpulumiprovidersgcp:default”,
“custom”: true,
“id”: “d6015732-4e21-4193-9d4c-08f86b2f5296”,
“type”: “pulumiprovidersgcp”,
“inputs”: {
“project”: “mindbody-staging”
}
},
orange-tailor-85423
05/09/2019, 9:45 PM{
“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 PMok
orange-tailor-85423
05/09/2019, 9:46 PMso 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 PMdefine environment in this case - the place where the pulumi CLI runs?
orange-tailor-85423
05/09/2019, 9:49 PMor something in the GCP env itself