[Feature] - Set resolve based hostname for http synthetic

[jeffbeagley]

Is your feature request related to a problem? Please describe.
I need to run a synthetic check against an Azure Application Gateway that has many listeners on it with host based routing. It appears that setting the Host header record is simply not enough. This can be verified using curl against any Application Gateway and works only when providing the --resolve flag.

Describe the resource you would like to have implemented.
elasticstack_kibana_synthetics_monitor

Describe the solution you'd like
Provide a way to provide the backend hostname, or respect the host header that can be provided via request_header

[tobio]

@jeffbeagley are you able to achieve this outside of Terraform, i.e manually through Kibana?

If so, it would be great to include the steps you need to take there to get this working. If not we'll have to transfer this issue to Kibana so they can support this at the API level before we can add support in the provider.

[jeffbeagley-basspro]

@jeffbeagley are you able to achieve this outside of Terraform, i.e manually through Kibana?

If so, it would be great to include the steps you need to take there to get this working. If not we'll have to transfer this issue to Kibana so they can support this at the API level before we can add support in the provider.

It is not available. I currently disabled tls verification so I can at least monitor one of my certificates but not sure how this will scale when I add multiple listeners/certificates to the app gateway.