terraform-provider-citrixadc

Citrix ADC Provider

The Citrix ADC provider is used to configure target ADC instances using the NITRO API.

Example Usage

# Simplest and least secure configuration
# Use http and default values for username and password
provider "citrixadc" {
  endpoint = "http://10.0.0.1"
}


# Use https and non default password
provider "citrixadc" {
  endpoint = "https://10.0.0.1"
  username = "nsroot"
  password = "secret"

  # Do not error due to non signed ADC TLS certificate
  # Can skip this if ADC TLS certificate is trusted
  insecure_skip_verify = true
}


# Proxy calls through NetScaler Console
# Login credentials refer to NetScaler Console
# Target ADC is referred by its ip address
provider "citrixadc" {
  endpoint   = "https://10.22.0.1"
  username   = "nsroot"
  password   = "admpassword"
  proxied_ns = "10.0.0.1"
}

# Target non default partition
provider "citrixadc" {
  endpoint   = "https://10.22.0.1"
  username   = "nsroot"
  password   = "admpassword"
  do_login   = true
  partition  = "par1"
}

# Proxy calls through NetScaler Console Service
# When using NetScaler Console Cloud:
# - endpoint: Your NetScaler Console Cloud URL (e.g., https://alps.adm.cloudburrito.com/)
# - username: API Client ID 
# - password: API Client Secret 
# - proxied_ns: IP of the target NetScaler instance (must be managed by NetScaler Console)
# - is_cloud: Set to true for NetScaler Console Cloud
# - do_login: Set to true to establish session
provider "citrixadc" {
  endpoint   = "https://<<ADM_CLOUD_URL>>/"
  username   = "<<USERNAME>>"
  password   = ""
  proxied_ns = "<<NS_IP>>"
  is_cloud   = true
  do_login   = true
}

# Fail fast when a target instance may be unreachable
# Bound each NITRO request to 5 seconds instead of waiting on the
# operating system's TCP connection timeout. Useful when managing many
# instances where some may be offline.
provider "citrixadc" {
  endpoint     = "https://10.0.0.1"
  http_timeout = 5
}

Argument Reference

The following arguments are supported.

!> Avoid hard coding credentials in terraform configuration files. It presents a security risk especially if they are committed and published in version control systems.