feat(zero_trust_organization): support v4 to v5 migration #124
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.
Supports v4 to v5 migration for
zero_trust_organizationresource.Import-only Resource Pattern
NOTE: This is an import-only resource. It does not get created by terraform, but instead only gets edited by terraform. The e2e tests make the assumption that zero trust is already set up through dash for testing accounts. The following changes were made to support this pattern:
tf-migrate:import-address=${var.cloudflare_account_id})Changes
zero_trust_access_organization,access_organizationEnd To End Tests
======================================== ✓ E2E Test Complete! ======================================== Summary: Step 1: v4 terraform apply Status: ✓ SUCCESS Step 2: Migration (v4 → v5) Status: ✓ SUCCESS Step 3: v5 plan (before apply) Status: ✓ No changes needed Step 4: v5 terraform apply Status: ✓ SUCCESS Step 5: v5 plan (after apply) Status: ✓ SUCCESS - Stable state achieved Result: No changes detected