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

AWS Route 53 health check search string error #6393

Closed
ghost opened this issue Nov 7, 2018 · 2 comments · Fixed by #6460
Closed

AWS Route 53 health check search string error #6393

ghost opened this issue Nov 7, 2018 · 2 comments · Fixed by #6460
Labels
service/route53 Issues and PRs that pertain to the route53 service.

Comments

@ghost
Copy link

ghost commented Nov 7, 2018

This issue was originally opened by @willettmeister as hashicorp/terraform#19230. It was migrated here as a result of the provider split. The original body of the issue is below.


When configuring a Route53 health check I am not able to specify a search string for either a http or https health check type. This seems to be contrary to the AWS documentation and I am able to add search string in a https health check.

Terraform version output:

Terraform v0.11.8

  • provider.aws v1.41.0
  • provider.template v1.0.0
@bflad
Copy link
Contributor

bflad commented Nov 14, 2018

Closing as a duplicate of #6346 as its from the same original author and that issue has more details/discussion. 👍

@bflad bflad closed this as completed Nov 14, 2018
@ghost
Copy link
Author

ghost commented Apr 2, 2020

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. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
service/route53 Issues and PRs that pertain to the route53 service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant