exoscale_kms_key (Resource)

Manage Exoscale KMS Keys.

Schema

Required

• name (String) ❗ The name of the KMS Key.
• zone (String) ❗ The Exoscale Zone name.

Optional

• description (String) ❗ A description of the KMS Key.
• multi_zone (Boolean) ❗ Whether the key is replicated across multiple zones.
• timeouts (Block, Optional) (see below for nested schema)
• usage (String) ❗ The key usage purpose (e.g. encrypt-decrypt).

Read-Only

• id (String) The ID of this resource.
• status (String) The current status of the KMS Key.

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.