-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
provider/aws: Add validation of Health Check target to aws_elb. #8578
provider/aws: Add validation of Health Check target to aws_elb. #8578
Conversation
Resolves #8547. |
Tests are passing:
|
As per @stack72, I will add more validation here to cover more cases. |
4a281d6
to
c697f2f
Compare
Tests (more) passing:
|
This commit adds a simple validation of the target in the Health Check block in order to reduce the number of issues related to the type, port and path values, especially when the TCP and SSL type was used. Signed-off-by: Krzysztof Wilczynski <krzysztof.wilczynski@linux.com>
c697f2f
to
bcaac02
Compare
Hi @kwilczynski This LGTM! Tests are green :)
|
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
This commit adds a simple validation of the target in the Health Check block in
order to reduce the number of issues related to the type, port and path values,
especially when the TCP and SSL type was used.
Signed-off-by: Krzysztof Wilczynski krzysztof.wilczynski@linux.com