Closed gleb-jiji closed 11 months ago
Are you able to work around this by performing a PULUMI_ENABLE_LEGACY_PLUGIN_SEARCH pulumi refresh
? Depending on the underlying state issue, this should cause a read of the resource along with attempting to write it to the state using the newer version of the plugin (assuming you have the 4.0 resource plugin installed).
With version 4.0 of the python library, PULUMI_ENABLE_LEGACY_PLUGIN_SEARCH=true pulumi refresh
produces a bunch of
* HTTP status 400: Could not route to /zones/dns_records/88f61edb99a9dc44932285f3cddbcdb3, perhaps your object identifier is invalid? (7003), No route for that URI (7000)
one for each Record
I have. I have both 3.5 and 4.0 resource plugins in ~/.pulumi/plugins
Just a pulumi refresh
succeeds but doesn't solve the issue.
Thanks for the update @gleb-jiji -- a plain refresh succeeding makes sense (since it'll use the 3.5 version of the plugin) whereas with that env var set, pulumi will attempt to use the latest version of the plugin. It looks like the identifiers may have even changed between versions somehow? Else, it's very odd that it cannot perform a read against those records. One other idea for how to move forward here would be to manually fix up the state via pulumi stack export
and editing the resulting JSON to have initialSettings
be an array and then importing the state via pulumi stack import
Since this is a virtual resource I might as well just delete it from the state. Should I create a more complete reproducible example?
Thanks for offering, but I don't think it's necessary. From https://github.com/cloudflare/terraform-provider-cloudflare/commit/49ba3a43633adbbc185f5f3881ecaa3c1e9b8fc2#diff-c4993bf7897ba11d3fd5d356a5c80d40d54ef3650adfe90a1180ae8e047f1858 we can see the change in schema to go from MaxItems: 1 to allowing the array, which will cause this type of breakage as there doesn't seem to be any corresponding migration for this.
With the Cloudflare provider being in 5.x version now, I don't think we'll do anything about 3.x to 4.x migration anymore
Hello!
Issue details
Upgrading from 3.5 to 4.0 with an existing
ZoneSettingsOverride
resource breaks with anUnexpected type
error.Steps to reproduce
pulumi-cloudflare
from 3.5 to 4.0 and runpulumi up
.Pulumi and package versions
``` $ pulumi version v3.18.1 $ pip list Package Version ------------------ --------- Arpeggio 1.10.2 attrs 21.2.0 awscli 1.22.11 beautifulsoup4 4.10.0 botocore 1.23.11 certifi 2021.10.8 charset-normalizer 2.0.7 cloudflare 2.8.15 colorama 0.4.3 dill 0.3.4 docutils 0.15.2 grpcio 1.42.0 idna 3.3 jmespath 0.10.0 jsonlines 2.0.0 parver 0.3.1 pip 21.0.1 protobuf 3.19.1 pulumi 3.18.1 pulumi-aws 4.29.0 pulumi-cloudflare 4.0.0 pulumi-hcloud 1.7.0 pyasn1 0.4.8 python-dateutil 2.8.2 PyYAML 5.4.1 requests 2.26.0 rsa 4.7.2 s3transfer 0.5.0 semver 2.13.0 setuptools 54.1.2 six 1.16.0 soupsieve 2.3.1 urllib3 1.26.7 wheel 0.36.2 ```Expected: Seamless provider version upgrade. Actual: