Hi all I m upgrading from v3 5 0 to v4 1 0 of the Cloudflare

Question

Hi all I m upgrading from v3 5 0 to v4 1 0 of the Cloudflare provider <https www pulumi com registry packages cloudflare > This is resulting in a bunch of replacements because the resource URN changes ` provider urn pulumi cloudflare dns secondary domains cloudflare dns secondary domains pulumi providers cloudflare default 3 0 0 3a22f721 09b3 4061 965f 6d1a97f600f4 = gt urn pulumi cloudflare dns secondary domains cloudflare d urn pulumi cloudflare dns secondary domains cloudflare dns secondary domains pulumi providers cloudflare default 4 0 0 output lt string gt ` Is this expected behaviour because there s a breaking change in the upstream TF provider What s the best way of dealing with this

prehistoric-activity-61023 · Answer

if you see updates to provider resource only that s the expected behavior

prehistoric-activity-61023 · Answer

actually let me take a look into that I think I m gonna have the same upgrade in one of my projects

prehistoric-activity-61023 · Answer

In my case it wants to create replacements for each Record resource too Although the only change is additional `allowOverwrite` property set to `false` thinking face I ve found the following GH issue <https github com pulumi pulumi cloudflare issues 186>

prehistoric-activity-61023 · Answer

In my case the URN of the provider doesn t change although its version is altered but that s understandable < victorious cat 95191> Do you use default provider configuration or do you create an explicit provider instance within pulumi code

prehistoric-activity-61023 · Answer

it should not affect the discussed case but I want to know if your case is related to 186 or it s something else and should be reported separately

victorious-cat-95191 · Answer

< prehistoric activity 61023> It s trying to replace all of the Record resources sorry I wasn t clear I m using the default provider configuration Looks like that Github issue is relevant

billowy-army-68599 · Answer

< victorious cat 95191> if it s just the urn changing you might be able to use aliases to stop the replacement

victorious-cat-95191 · Answer

< billowy army 68599> Thanks I ve had a quick look at that and it doesn t work The Record resource URN doesn t change so adding an alias there doesn t help It s the URN for the provider within the record resource that causes the Record to be replaced I guess I ll have to wait for progress on that GIthub issue before I can upgrade

victorious-cat-95191 · Answer

I manually modified the stack to change the provider to the new version and Pulumi was still trying to replace the Record resources so it looks like it might be to do with the additional `allowOverwrite`property man shrugging

prehistoric-activity-61023 · Answer

I tried to do some hacks on my part as well with no success I d need to look deeper how the plugin code works and why it forces the replacement instead of update so the additional property `allowOverwrite` is saved with default value

prehistoric-activity-61023 · Answer

I m afraid it might be related to the way TF plugin works because I noticed that this plugin is ported from terraform Still right now I cannot help more If I were you I d stick to v3 for now and wait until the GH issue is resolved

victorious-cat-95191 · Answer

Indeed I m also struggling to reconcile the changes from this breaking change in the TF provider resource cloudflare record `data` is now a `TypeList` instead of a `TypeMap` <https github com cloudflare terraform provider cloudflare blob master CHANGELOG md 300 september 20th 2021> so happy to stay at v3 for now