-
Notifications
You must be signed in to change notification settings - Fork 624
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
Custom Health Check Target Type not available in Terraform #2766
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Thank you for reporting this issue! For maintainers to dig into issues it is required that all issues include the entirety of This issue has been marked with |
One other interesting thing of note is that when the terraform plan is done, it shows all the right stuff, but when it gets executed, the Health Check Target is of course set to Default, but the Helath Check Target Address is the same as the Customer endpoint, even if it's configured and shows as proper in the terraform plan. |
Marking this issue as stale due to 30 days of inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 7 days it will automatically be closed. Maintainers can also remove the |
This issue was closed because it has been stalled for 7 days with no activity. |
Confirmation
Terraform and Cloudflare provider version
When using terraform to set the ipsec tunnel information, there is not an option to set the Health check target type from Default to Custom:
Affected resource(s)
ipsec_tunnel
Terraform configuration files
Link to debug output
https://github.com/cloudflare/terraform-provider-cloudflare/issues/new?assignees=&labels=kind%2Fbug%2Cneeds-triage&projects=&template=bug_report.yml
Panic output
No response
Expected output
Be able to set to Custom
Actual output
Shows as Default
Steps to reproduce
Set a ipsectunnel configuration via terraform and it doens't allow for Health check target type to be set from Default to Custom
Additional factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: