exoscale_dbaas_pg_user (Resource)

❗ Manage service users for a PostgreSQL Exoscale Database Services (DBaaS).

Schema

Required

  • service (String) ❗ The name of the database service.
  • username (String) ❗ The name of the user for this service.
  • zone (String) ❗ The Exoscale Zone name.

Optional

Read-Only

  • id (String) The ID of this resource, computed as service/username
  • password (String, Sensitive) The password of the service user.
  • type (String) The type of the service user.

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.