You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use terraform and the cloudflare-terraform provider to manage all/most of our Cloudflare services and settings. Cache Reserve is currently not available in either. When we asked our Cloudflare reps we were told it would eventually become available once Cache Reserve is out of beta
The primary goal for us is to be able to get the ability to configure Cache Reserve via terraform. For that to be possible, cloudflare-go needs to support this capability so that it can be added to https://github.com/cloudflare/terraform-provider-cloudflare (will create a feature request issue there as well)
At present, we manage everything through Terraform, except for Cache Reserve which we enable manually in the dashboard. This is less than ideal for companies relying on IaC and gitops processes.
Current cloudflare-go version
v0.66.0
Description
Cache Reserve appear to have come out of beta recently (see cloudflare/cloudflare-docs#8561)
We use terraform and the cloudflare-terraform provider to manage all/most of our Cloudflare services and settings. Cache Reserve is currently not available in either. When we asked our Cloudflare reps we were told it would eventually become available once Cache Reserve is out of beta
Handy links:
Use cases
The primary goal for us is to be able to get the ability to configure Cache Reserve via terraform. For that to be possible, cloudflare-go needs to support this capability so that it can be added to https://github.com/cloudflare/terraform-provider-cloudflare (will create a feature request issue there as well)
At present, we manage everything through Terraform, except for Cache Reserve which we enable manually in the dashboard. This is less than ideal for companies relying on IaC and gitops processes.
Potential cloudflare-go usage
References
No response
The text was updated successfully, but these errors were encountered: