Adam Barclay

I have run the program again with verbose logging. It's a 758MB log file, 59MB zipped if you are interested, or is there anything in particular I could extract perhaps?

Further to this, the deletion of the stack resources takes a _very_ long time, which suggests a bottleneck somewhere in the node/go SDK. 412 deletions took 1h 4m. Most of...

A further update... I've been trying to get this to work by sequencing the updates. I'm doing this with a custom, empty resource, `Region`, that I have as the parent...

@jeremydmiller Many thanks. It's not ideal what I'm doing here, granted (I will look at improving :)), but this did indeed use to work in v3.

@jeremydmiller Based on the frequency and investigation I think you are right that the root cause is transient, I think the issue here is the response to that transient exception....

Hi @iwahbe. Do you mean by making a change in the state beforehand?

@AaronFriel sorry for the delay, I have just turned my attention back towards the upgrade. According to the Pulumi portal all field values have changed:  I'm not sure if...

I use the automation engine, so have grabbed the resourcePreEvent that shows the calculated diffs: ````json { "sequence": 86, "timestamp": 1683797799, "resourcePreEvent": { "metadata": { "op": "create-replacement", "urn": "urn:pulumi:uat-deploy-global::s365-analytics::cloudflare:index/record:Record::analytics-ingestion-cname", "type":...

I have upgraded CLI and npm to version 3.53.1 and still experience the above issue. Alongside the Azure Native issue referenced above I'm completely unable to manage our node pools...

I have just upgraded to the latest, v3.68.0 and I still get this issue. I have not attempted to reduce to a minimum working repro. The current instance of this...