terraform/website/source/docs/providers/ultradns/r/probe_http.html.markdown

99 lines
2.8 KiB
Markdown
Raw Normal View History

ultradns providers and improvements (#9788) * vendor: update github.com/Ensighten/udnssdk to v1.2.1 * ultradns_tcpool: add * ultradns.baseurl: set default * ultradns.record: cleanup test * ultradns_record: extract common, cleanup * ultradns: extract common * ultradns_dirpool: add * ultradns_dirpool: fix rdata.ip_info.ips to be idempotent * ultradns_tcpool: add doc * ultradns_dirpool: fix rdata.geo_codes.codes to be idempotent * ultradns_dirpool: add doc * ultradns: cleanup testing * ultradns_record: rename resource * ultradns: log username from config, not client udnssdk.Client is being refactored to use x/oauth2, so don't assume we can access Username from it * ultradns_probe_ping: add * ultradns_probe_http: add * doc: add ultradns_probe_ping * doc: add ultradns_probe_http * ultradns_record: remove duplication from error messages * doc: cleanup typos in ultradns * ultradns_probe_ping: add test for pool-level probe * Clean documentation * ultradns: pull makeSetFromStrings() up to common.go * ultradns_dirpool: log hashIPInfoIPs Log the key and generated hashcode used to index ip_info.ips into a set. * ultradns: simplify hashLimits() Limits blocks only have the "name" attribute as their primary key, so hashLimits() needn't use a buffer to concatenate. Also changes log level to a more approriate DEBUG. * ultradns_tcpool: convert rdata to schema.Set RData blocks have the "host" attribute as their primary key, so it is used by hashRdatas() to create the hashcode. Tests are updated to use the new hashcode indexes instead of natural numbers. * ultradns_probe_http: convert agents to schema.Set Also pull the makeSetFromStrings() helper up to common.go * ultradns: pull hashRdatas() up to common * ultradns_dirpool: convert rdata to schema.Set Fixes TF-66 * ultradns_dirpool.conflict_resolve: fix default from response UltraDNS REST API User Guide claims that "Directional Pool Profile Fields" have a "conflictResolve" field which "If not specified, defaults to GEO." https://portal.ultradns.com/static/docs/REST-API_User_Guide.pdf But UltraDNS does not actually return a conflictResolve attribute when it has been updated to "GEO". We could fix it in udnssdk, but that would require either: * hide the response by coercing "" to "GEO" for everyone * use a pointer to allow checking for nil (requires all users to change if they fix this) An ideal solution would be to have the UltraDNS API respond with this attribute for every dirpool's rdata. So at the risk of foolish consistency in the sdk, we're going to solve it where it's visible to the user: by checking and overriding the parsing. I'm sorry. * ultradns_record: convert rdata to set UltraDNS does not store the ordering of rdata elements, so we need a way to identify if changes have been made even it the order changes. A perfect job for schema.Set. * ultradns_record: parse double-encoded answers for TXT records * ultradns: simplify hashLimits() Limits blocks only have the "name" attribute as their primary key, so hashLimits() needn't use a buffer to concatenate. * ultradns_dirpool.description: validate * ultradns_dirpool.rdata: doc need for set * ultradns_dirpool.conflict_resolve: validate
2016-12-15 17:28:34 +01:00
---
layout: "ultradns"
page_title: "UltraDNS: ultradns_probe_http"
sidebar_current: "docs-ultradns-resource-probe-http"
description: |-
Provides an UltraDNS HTTP probe
---
# ultradns\_probe\_http
Provides an UltraDNS HTTP probe
## Example Usage
```
resource "ultradns_probe_http" "probe" {
zone = "${ultradns_tcpool.pool.zone}"
name = "${ultradns_tcpool.pool.name}"
pool_record = "10.2.1.1"
agents = ["DALLAS", "AMSTERDAM"]
interval = "ONE_MINUTE"
threshold = 1
http_probe {
transaction {
method = "POST"
url = "http://localhost/index"
transmitted_data = "{}"
follow_redirects = true
limit {
name = "run"
warning = 1
critical = 2
fail = 3
}
limit {
name = "avgConnect"
warning = 4
critical = 5
fail = 6
}
limit {
name = "avgRun"
warning = 7
critical = 8
fail = 9
}
limit {
name = "connect"
warning = 10
critical = 11
fail = 12
}
}
total_limits {
warning = 13
critical = 14
fail = 15
}
}
}
```
## Argument Reference
The following arguments are supported:
* `zone` - (Required) The domain of the pool to probe.
* `name` - (Required) The name of the pool to probe.
- `pool_record` - (optional) IP address or domain. If provided, a record-level probe is created, otherwise a pool-level probe is created.
- `agents` - (Required) List of locations that will be used for probing. One or more values must be specified. Valid values are `"NEW_YORK"`, `"PALO_ALTO"`, `"DALLAS"` & `"AMSTERDAM"`.
- `threshold` - (Required) Number of agents that must agree for a probe state to be changed.
- `http_probe` - (Required) an HTTP Probe block.
- `interval` - (Optional) Length of time between probes in minutes. Valid values are `"HALF_MINUTE"`, `"ONE_MINUTE"`, `"TWO_MINUTES"`, `"FIVE_MINUTES"`, `"TEN_MINUTES"` & `"FIFTEEN_MINUTE"`. Default: `"FIVE_MINUTES"`.
HTTP Probe block
- `transaction` - (Optional) One or more Transaction blocks.
- `total_limits` - (Optional) A Limit block, but with no `name` attribute.
Transaction block
- `method` - (Required) HTTP method. Valid values are`"GET"`, `"POST"`.
- `url` - (Required) URL to probe.
- `transmitted_data` - (Optional) Data to send to URL.
- `follow_redirects` - (Optional) Whether to follow redirects.
- `limit` - (Required) One or more Limit blocks. Only one limit block may exist for each name.
Limit block
- `name` - (Required) Kind of limit. Valid values are `"lossPercent"`, `"total"`, `"average"`, `"run"` & `"avgRun"`.
- `warning` - (Optional) Amount to trigger a warning.
- `critical` - (Optional) Amount to trigger a critical.
- `fail` - (Optional) Amount to trigger a failure.