Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

resource/cloudflare_argo_tunnel: rename to cloudflare_tunnel #2135

Merged
merged 1 commit into from
Jan 12, 2023

Conversation

jacobbednarz
Copy link
Member

No description provided.

@github-actions
Copy link
Contributor

changelog detected ✅

@jacobbednarz jacobbednarz mentioned this pull request Jan 12, 2023
38 tasks
@jacobbednarz jacobbednarz added this to the v4.0.0 milestone Jan 12, 2023
@jacobbednarz
Copy link
Member Author

TF_ACC=1 go test $(go list ./...) -v -run "^TestAccCloudflareTunnelCreate_" -count 1 -parallel 1 -timeout 120m -parallel 1
?   	github.com/cloudflare/terraform-provider-cloudflare	[no test files]
=== RUN   TestAccCloudflareTunnelCreate_Basic
--- PASS: TestAccCloudflareTunnelCreate_Basic (7.60s)
PASS
ok  	github.com/cloudflare/terraform-provider-cloudflare/internal/provider	8.160s
``

@jacobbednarz jacobbednarz merged commit fcf3831 into 4.x Jan 12, 2023
@jacobbednarz jacobbednarz deleted the rename-argo-tunnel-to-tunnel branch January 12, 2023 01:13
@github-actions github-actions bot modified the milestones: v4.0.0, v3.33.0 Jan 12, 2023
github-actions bot pushed a commit that referenced this pull request Jan 12, 2023
@jacobbednarz jacobbednarz modified the milestones: v3.33.0, v4.0.0 Jan 13, 2023
@github-actions
Copy link
Contributor

This functionality has been released in v4.0.0 of the Terraform Cloudflare Provider.

Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@carl-armis
Copy link

Would like to request more information on the proposed migration path for this change.

It would be useful to have both resource type names supported to allow for us to properly migrated. The sudden removal creates a bit of a loop for us.

@AllexVeldman
Copy link

@jacobbednarz Renaming the resource fails in terraform with

│ Warning: Missing resource schema from provider
│ 
│ No resource schema found for cloudflare_argo_tunnel when decoding prior
│ state
╵
╷
│ Error: no schema available for module.cf-argo-tunnel.cloudflare_argo_tunnel.argo-tunnel while reading state; this is a bug in Terraform and should be reported
│ 
│ 

As there is no version with both cloudflare_argo_tunnel and cloudflare_tunnel the only upgrade path we have is remove existing tunnel on v3, update, re-add tunnel in v4.

See https://developer.hashicorp.com/terraform/plugin/sdkv2/best-practices/deprecations#provider-data-source-or-resource-rename.

@afreyermuth98
Copy link

@jacobbednarz @AllexVeldman @carl-armis
Maybe we'll have more visibility if we re-open a new issue on this subject ? Because talking on a merged PR doesn't seem to be efficient :/

@AllexVeldman
Copy link

AllexVeldman commented Jul 7, 2023

I'm lucky to be in the position where I could destroy and recreate the tunnel and dependant resources.
But I agree an Issue makes this more visible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants