Upgrade terraform-provider-cloudflare to v5.22.0 - #1634
Merged
corymhall merged 3 commits intoJul 16, 2026
Conversation
pulumi-bot
enabled auto-merge (squash)
July 11, 2026 04:18
Does the PR have any schema changes?Found 342 breaking changes: Resources
New resources:
New functions:
Maintainer note: consult the runbook for dealing with any breaking changes. |
pulumi-bot
force-pushed
the
upgrade-terraform-provider-cloudflare-to-v5.22.0-ci
branch
4 times, most recently
from
July 15, 2026 04:17
8c26adf to
5a8620d
Compare
pulumi-bot
force-pushed
the
upgrade-terraform-provider-cloudflare-to-v5.22.0-ci
branch
from
July 16, 2026 04:17
5a8620d to
b39cd6b
Compare
Member
|
@pulumi-eon can you look into the CI failures and let me know what the fixes are? |
Eon ran into a problemRuntimeError: SSE stream inactive for 120s (no data received). Total elapsed: 451s Partial work may exist — see the session log. |
corymhall
disabled auto-merge
July 16, 2026 14:23
Upstream's terraform-provider-cloudflare v5.22.0 bumped cloud_connector_rules to schema version 500 (as part of a mechanical sweep bumping all remaining v5 resources to version 500), with a genuine no-op state upgrader from version 0. This trips the TestSchemaVersionsForResetResources canary, which asserts resources in resourcesWhichNeedSchemaVersionReset still declare schema version 0 upstream (see #1156). Since the new upstream migration is a real (albeit no-op) 0->500 upgrade path, and Pulumi state for this resource was always persisted at version 0 (the previous hard-coded reset), removing it from the reset list lets Terraform's own upgrade path run normally: recorded version 0 <= new version 500, so no downgrade error occurs, and the no-op upgrader preserves existing state exactly as before. This mirrors how cloudflare_custom_ssl and cloudflare_dns_record were previously handled in #1554 when upstream did the same kind of mechanical schema version bump for them.
corymhall
enabled auto-merge (squash)
July 16, 2026 14:46
corymhall
approved these changes
Jul 16, 2026
corymhall
deleted the
upgrade-terraform-provider-cloudflare-to-v5.22.0-ci
branch
July 16, 2026 15:26
Contributor
Author
|
This PR has been shipped in release v6.18.0. |
1 similar comment
Contributor
Author
|
This PR has been shipped in release v6.18.0. |
This was referenced Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was generated via
$ upgrade-provider pulumi/pulumi-cloudflare --kind=provider --target-bridge-version=latest --target-version=5.22.0 --allow-missing-docs=true.Fixes Upgrade terraform-provider-cloudflare to v5.22.0 #1633
Fixes Upgrade terraform-provider-cloudflare to v5.21.1 #1616
Fixes Upgrade terraform-provider-cloudflare to v5.21.0 #1611
Fixes Upgrade terraform-provider-cloudflare to v5.20.0 #1604