-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 support to google_compute_target_pool for health checks self_link #702
Conversation
…ealth check self_link
TF_ACC=1 go test ./google -v -run TestAccComputeTargetPool_basic -timeout 120m
=== RUN TestAccComputeTargetPool_basic
--- PASS: TestAccComputeTargetPool_basic (72.02s)
PASS |
|
||
hcLink := healthCheckRes.Primary.Attributes["self_link"] | ||
if targetPoolRes.Primary.Attributes["health_checks.0"] != hcLink { | ||
return fmt.Errorf("Health check not set up. Expected '%s'", hcLink) |
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.
fyi: '%s' is equivalent to %q (up to you if you want to change it)
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.
Will do
…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.
Signed-off-by: Modular Magician <[email protected]>
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! |
Instead of requiring the health check name. It now accepts the self_link or the name.
I added:
google_compute_http_health_check
is supported. This will prevent our user from being stuck like mentioned here: Update compute_health_check.html.markdown #300.MaxItems:1
in the schema. You can't have more than one. The API will fail. The official docs also says so.