» Aviatrix Provider

The Aviatrix provider is used to interact with the many resources supported by Aviatrix, which can be built upon various cloud infrastructure providers such as AWS, Azure, Google Cloud, and Oracle Cloud. It needs to be configured with the proper credentials before it can be used.

Use the navigation to the left to read about the available resources.

» Example Usage

# Configure Aviatrix provider
provider "aviatrix" {
  controller_ip           = "1.2.3.4"
  username                = "admin"
  password                = "password"
  skip_version_validation = false
  version                 = "2.5.0"
}

# Create an access account
resource "aviatrix_account" "my_acc" {
  # ...
}

» Authentication

The Aviatrix provider offers various means of providing credentials for authentication. The following methods are supported:

  • Static credentials
  • Environment variables

» Static credentials

Static credentials can be provided by specifying the controller_ip, username and password arguments in-line in the Aviatrix provider block:

Usage:

provider "aviatrix" {
  controller_ip           = "1.2.3.4"
  username                = "admin"
  password                = "password"
}

» Environment variables

You can provide credentials via the AVIATRIX_CONTROLLER_IP, AVIATRIX_USERNAME, AVIATRIX_PASSWORD environment variables, representing your Aviatrix controller's public IP, username and password of your Aviatrix access account, respectively.

provider "aviatrix" {}

Usage:

$ export AVIATRIX_CONTROLLER_IP="1.2.3.4"
$ export AVIATRIX_USERNAME="admin"
$ export AVIATRIX_PASSWORD="password"
$ terraform plan

» Argument Reference

The following arguments are supported:

» Required

  • controller_ip - (Required) Aviatrix controller's public IP.
  • username - (Required) Aviatrix account username which will be used to login to Aviatrix controller.
  • password - (Required) Aviatrix account password corresponding to above username.

» Optional

  • skip_version_validation - (Optional) Default: false. If set to true, it skips checking whether current Terraform provider supports current Controller version.
  • version - (Optional) - Specify Aviatrix provider release version number. If not specified, Terraform will automatically pull and source the latest release.