exoscale_nlb_service_list (Data Source)

Fetch Exoscale Network Load Balancers (NLB) Services.

Corresponding resource: exoscale_nlb.

Example Usage

data "exoscale_nlb_service_list" "example_nlb_services" {
  name = "my-nlb"
}

# Outputs
output "nlb_services_output" {
  value = data.exoscale_nlb_service_list.example_nlb_services.services
}

Please refer to the examples directory for complete configuration examples.

Schema

Required

  • zone (String) The Exoscale Zone name.

Optional

  • nlb_id (String) The NLB ID to match (conflicts with name).
  • nlb_name (String) The NLB name to match (conflicts with id).
  • timeouts (Block, Optional) (see below for nested schema)

Read-Only

Nested Schema for timeouts

Optional:

  • 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.

Nested Schema for services

Read-Only:

  • description (String) NLB service description.
  • healthcheck (Object) (see below for nested schema)
  • id (String) NLB service ID.
  • instance_pool_id (String) The exoscale_instance_pool (ID) to forward traffic to.
  • name (String) NLB Service name.
  • port (Number) Port exposed on the NLB’s public IP.
  • protocol (String) Network traffic protocol.
  • state (String) NLB Service State.
  • strategy (String) The strategy (round-robin|source-hash).
  • target_port (Number) Port on which the network traffic will be forwarded to on the receiving instance.

Nested Schema for services.healthcheck

Read-Only:

  • interval (Number)
  • mode (String)
  • port (Number)
  • retries (Number)
  • timeout (Number)
  • tls_sni (String)
  • uri (String)