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

Add enabled field to load_balancer (#208) #281

Merged

Conversation

SteveGoldthorpe-Work
Copy link

Adds support for enabled field in load-balancers (#208).
Load balancers that have been disabled via the dashboard (or other tooling) will want to change to enabled, you should add the field 'enabled: false' to them to match their current state.
Load balancers purely managed via terraform will be fine as there was no way to disable them before.

@ghost ghost added the size/XS label Apr 2, 2019
@ghost ghost added the kind/documentation Categorizes issue or PR as related to documentation. label Apr 2, 2019
@patryk patryk merged commit 0ca8e72 into cloudflare:master Apr 2, 2019
@patryk
Copy link

patryk commented Apr 2, 2019

Looks good, thank you @SteveGoldthorpe-Work !

boekkooi-lengoo pushed a commit to boekkooi-lengoo/terraform-provider-cloudflare that referenced this pull request Feb 28, 2022
While looking into an issue in the Terraform provider, I've found that
the `correlate` values for rate limiting are always being sent
regardless of whether the value is set or not. This isn't really a big
deal as I'm assuming the API endpoint just disregard it but for the
Terraform provider, it does make the state management more difficult and
messy than what it needs to be due to the nested types.

Instead of always sending the value, I've updated the struct to allow
`nil` and to omit when the values are empty resulting in a fix for the
issues downstream.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. size/XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants