-
Notifications
You must be signed in to change notification settings - Fork 626
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
Add CH Fallback Origin resources #757
Add CH Fallback Origin resources #757
Conversation
Hi @cdloh, yes, |
@patryk should it also be doing that for custom hostnames then? At present the module isn't unless it's doing it in a different manner. |
cloudflare/resource_cloudflare_custom_hostname_fallback_origin.go
Outdated
Show resolved
Hide resolved
cloudflare/resource_cloudflare_custom_hostname_fallback_origin.go
Outdated
Show resolved
Hide resolved
cloudflare/resource_cloudflare_custom_hostname_fallback_origin.go
Outdated
Show resolved
Hide resolved
Yep, if that's been missed, we can add it as a condition. |
# By Jacob Bednarz (3) and others # Via GitHub (4) and Callum Loh (1) * master: Restore custom_hostname resource accidentally removed in cloudflare#749 Add support for configuring authenticated origin pulls (cloudflare#749) Update CHANGELOG.md ci: fix website-test Update CHANGELOG.md Add more info on cloudflare_zones data source breaking change Compare firewall descriptions after converting unicode + HTML entities Update CHANGELOG.md Support Spectrum applications with port ranges # Conflicts: # cloudflare/provider.go
f840365
to
ddcb982
Compare
As this is a single endpoint/resource, running these in parallel results in race conditions and misleading errors.
Allows us some flexibility if the domain changes.
As custom hostname fallback origin is a single resource, it's possible that we can introduce our own race conditions to update it which will fail if the remote API is having any type of lag in showing updated resources. To combat this, we can introduce a retry mechanism on requests that don't end up in a "pending_deployment" to help smooth out the experience.
Hey @cdloh, thanks for all this! I've gone ahead and pushed up a few changes as the integration test suite wasn't consistently working and these got it to that happy place. Feel free to step through the individual commits however the summary is:
I'm going to give this another look over in a few hours after I've stepped away but I think we're nearly ready to merge this one. |
d2d3060
to
49ba05a
Compare
Thanks for your persistence here @cdloh! This is great! 🌟 |
support account-level logpush jobs
I've added what unit tests I can, but I don't have an account I'm able to run the full suite across. Wasn't sure if you'd want update tests for this as well.
I've set the id to be
zoneid
-custom_hostname_fallback_origin as the API doesn't return a nice ID to use.Not sure if I should set ForceNew for zoneid?
anyway thoughts / comments.