exoscale_dbaas_pg_connection_pool (Resource)

Manage PostgreSQL PgBouncer connection pools for an Exoscale Database Services (DBaaS).

Schema

Required

• database_name (String) ❗ The PostgreSQL database name targeted by this pool.
• name (String) ❗ The connection pool name.
• service (String) ❗ The name of the PostgreSQL database service.
• zone (String) ❗ The Exoscale Zone name.

Optional

• mode (String) The PgBouncer pool mode (transaction, statement, or session).
• size (Number) The connection pool size.
• timeouts (Block, Optional) (see below for nested schema)
• username (String) ❗ The PostgreSQL username used by this pool.

Read-Only

• connection_uri (String, Sensitive) The connection URI for this pool.
• id (String) The ID of this resource, computed as service/name.

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.