exoscale_dbaas_external_endpoint_elasticsearch (Resource)

Manage Exoscale DBaaS External Endpoint for Elasticsearch logs integration.

Schema

Required

• index_prefix (String) Elasticsearch index prefix.
• name (String) ❗ The endpoint name.
• url (String) Elasticsearch connection URL.
• zone (String) ❗ The Exoscale Zone name.

Optional

• ca (String, Sensitive) PEM encoded CA certificate.
• index_days_max (Number) Maximum number of days of logs to keep (1-10000).
• timeout (Number) Elasticsearch request timeout in seconds (10-120).
• timeouts (Block, Optional) (see below for nested schema)

Read-Only

• id (String) The ID of this resource.

Nested Schema for timeouts

Optional:

• create (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as “30s” or “2h45m”. Valid time units are “s” (seconds), “m” (minutes), “h” (hours).
• delete (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as “30s” or “2h45m”. Valid time units are “s” (seconds), “m” (minutes), “h” (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
• read (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as “30s” or “2h45m”. Valid time units are “s” (seconds), “m” (minutes), “h” (hours). Read operations occur during any refresh or planning operation when refresh is enabled.
• update (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as “30s” or “2h45m”. Valid time units are “s” (seconds), “m” (minutes), “h” (hours).

-> The symbol ❗ in an attribute indicates that modifying it, will force the creation of a new resource.