Hey team! I've opened three issues related to our v5 -> v6 upgrade: 1.

cloudflare.List

— Duplicate Set Element on state migration— Inline`Items` in existing state fail to deserialize after upgrading, blocking

pulumi preview

entirely. I can contribute a fix for this — other resources already handle similar migrations via `PreStateUpgradeHook`/`TransformFromState`, so the pattern exists (link). 2.

ZoneSubscription

— 404 for free-plan zones— Creating or importing a subscription for free zones fails even though

"free"

is listed as a valid

RatePlan.Id

in the docs (link). 3.

ManagedHeaders

— Required fields should be Optional —

ManagedRequestHeaders

and

ManagedResponseHeaders

are both marked Required in v6, but the Cloudflare API supports partial updates and v5 had them as Optional (link). All three issues seem to originate from the upstream Terraform provider (

cloudflare/terraform-provider-cloudflare

) — the v5 provider was auto-generated from the Cloudflare OpenAPI spec, and these problems were carried over through

pulumi-terraform-bridge

. Should I also file these upstream on the Terraform provider repo, or is it expected that the Pulumi team will coordinate with Cloudflare on this?

If the issues exhibit themselves in a similar TF program, you can file an issue in the upstream provider and link it in your Pulumi issue. Pulumi will usually automatically upgrade and release a new version of our provider when the upstream TF provider updates. Coordination (and whether the upstream will promptly accept a fix from us) really varies by provider. Some provider maintainers are friendly and responsive, others, less so. (I don't have any experience with Cloudflare specifically, so I can't comment on what it's like trying to work with them.)