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
[feat] Load Balancers, User LB Monitors, User LB Pools #142
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Would just link to see a link in the README.
README.md
Outdated
@@ -34,6 +34,7 @@ The current feature list includes: | |||
- [ ] [Railgun](https://www.cloudflare.com/railgun/) administration | |||
- [ ] [Keyless SSL](https://blog.cloudflare.com/keyless-ssl-the-nitty-gritty-technical-details/) | |||
- [x] [Origin CA](https://blog.cloudflare.com/universal-ssl-encryption-all-the-way-to-the-origin-for-free/) | |||
- [x] Load Balancing (user pools and monitors only) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Linked to the blog post - the marketing page is too concise for my liking!
I like the org approach. Less API surface, and clearer intent. Add to the PR, @cbranch - ? |
Implemented by creating the API object with an 'Organization' option. The supposition is that API users probably only care about updating zones within a single scope, so creating separate APIs for both organization and account is unnecessary.
Added a bug fix when modifying load balancers that use Automatic TTLs. |
A suggestion for how we may support organization-level pools and monitors is presented in the load-balancing-org branch (and possibly, how to support the same for Railguns)