Update compute_health_check.html.markdown #300
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Mention limitation of non HTTP health checks with TargetPools to hopefully save other people getting stuck like I did :)
selmanj
suggested changes
Aug 9, 2017
| @@ -10,7 +10,7 @@ description: |- | |||
|
|
|||
| Manages a health check within GCE. This is used to monitor instances | |||
| behind load balancers. Timeouts or HTTP errors cause the instance to be | |||
| removed from the pool. For more information, see [the official | |||
| removed from the pool. This cannot be used with GCE `TargetPools` as they only support `HttpHealthChecks`. For more information, see [the official | |||
There was a problem hiding this comment.
I agree that this behavior is confusing.
However it would be nicer to make the documentation match the public API closer. Maybe something like:
Be aware that if you're managing a [Network Load Balancer](https://cloud.google.com/compute/docs/load-balancing/network/), you must use one of `google_compute_http_health_check` or `google_compute_https_health_check` instead of this resource. See [Legacy Health Checks](https://cloud.google.com/compute/docs/load-balancing/health-checks#legacy_health_checks) for more information.better explanation, more in line with official GCE docs
|
Sorry, I know you made the requested changes, but after talking to others it makes more sense to document this on the TargetPool resource documentation itself. Specifically in |
|
I will update the target pool documentation in a separate PR. |
rosbo
added a commit
that referenced
this pull request
Nov 8, 2017
…#702) - Accepts self_link in addition of health check name - Removes the need for an API call to generate the self link - Improves the documentation to mention that only the legacy google_compute_http_health_check is supported. This will prevent our user from being stuck like mentioned here: #300. - Adds a MaxItems:1 in the schema. You can't have more than one. The API will fail. The official docs also says so. - Adds a check to the acceptance test to ensure the health checks are properly setup.
chrisst
pushed a commit
to chrisst/terraform-provider-google
that referenced
this pull request
Nov 9, 2018
…hashicorp#702) - Accepts self_link in addition of health check name - Removes the need for an API call to generate the self link - Improves the documentation to mention that only the legacy google_compute_http_health_check is supported. This will prevent our user from being stuck like mentioned here: hashicorp#300. - Adds a MaxItems:1 in the schema. You can't have more than one. The API will fail. The official docs also says so. - Adds a check to the acceptance test to ensure the health checks are properly setup.
luis-silva
pushed a commit
to luis-silva/terraform-provider-google
that referenced
this pull request
May 21, 2019
…ds (hashicorp#300) <!-- This change is generated by MagicModules. --> /cc @rileykarson
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mention limitation of non HTTP health checks with TargetPools to hopefully save other people getting stuck like I did :)