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
[Resources: cloudflare_argo] Tiered Cache Topology selection needed #996
Comments
At the time of writing, there isn't a public API endpoint support for this so we can't yet add anything to |
Tracking this issue as Seismic Software has a need for this as well. |
This appears to be supported via an undocumented API endpoint. To enable smart topology:
To enable smart topology and use generic:
|
@jacobbednarz any chance to have this feature added to cloudflare-go (and, subsequently, to the CF provider) now that there's an (undocumented) API endpoint for this? I'm hoping that the fact this API is undocumented should not be an issue, because |
I'm afraid the endpoint needs to be publicly documented before using it in Terraform or the SDK. I'd recommend opening a support ticket to get it routed to the service team to action. |
FYI @jacobbednarz I got this submitted via a support request, and after a few days got this resolution response:
While it doesn't seem to be done yet, hopefully it will be soon. |
this has landed in v3.31.0 via #2101 |
Current Terraform version
Terraform version v0.14.4
Description
As in https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/argo - cloudflare provider 2.19.2
supports enabling of tiered_caching and smart_routing, But it doesn't support selection of Tiered Cache Topology for tiered_caching.
Use cases
Currently we have to switch the Tiered Cache Topology in web ui, while the state we keep in terraform.
Potential Terraform configuration
References
No response
Currently we have to switch the Tiered Cache Topology in web ui, while the state we keep in terraform.
The lack of the feature Tiered Cache Topology may be an issue for projects with a large number of domains .
The text was updated successfully, but these errors were encountered: