Transactional endpoint

Creates or updates a transactional endpoint.

Example

resource "akamai_botman_transactional_endpoint" "transaction_endpoint" {
  config_id              = data.akamai_appsec_configuration.configuration.config_id
  security_policy_id     = "gms1_134637"
  transactional_endpoint = file("${path.module}/transactional_endpoint.json")
  operation_id           = "e0f89bb0-77d5-46f7-979d-e204e6fdc5a5"
}

Argument reference

This resource supports the following arguments:

• config_id (Required). Unique identifier of the security configuration associated with the transactional endpoint.
• security_policy_id (Required). Unique identifier of the security policy associated with the transactional endpoint.
• operation_id (Required). Unique identifier of the API operation being created or updated.
• transactional_endpoint (Required). JSON collection of transactional endpoint settings and setting values. In the preceding sample code, the syntax file("${path.module}/transactional_endpoint.json") points to the location of a JSON file containing the transactional endpoint settings and values. Use the Bot Manager API or Bot Manager in Akamai Control Center to create a configuration. Then, export your configuration or use the corresponding data source to get the JSON file.