Terraform Provider

NOTE: We are in the process of planning v2 of the provider which will not be backwards compatible. See the v2Plan for further details.

• Website: https://www.terraform.io
• 
• Mailing list: Google Groups

Requirements

• Terraform 0.10.x
• Go 1.8 (to build the provider plugin)

Building The Provider

Clone repository to: $GOPATH/src/github.com/terraform-providers/terraform-provider-vcd

$ mkdir -p $GOPATH/src/github.com/terraform-providers; cd $GOPATH/src/github.com/terraform-providers
$ git clone [email protected]:terraform-providers/terraform-provider-vcd

Enter the provider directory and build the provider

$ cd $GOPATH/src/github.com/terraform-providers/terraform-provider-vcd
$ make build

Using the provider

Fill in for each provider

Developing the Provider

If you wish to work on the provider, you'll first need Go installed on your machine (version 1.8+ is required). You'll also need to correctly setup a GOPATH, as well as adding $GOPATH/bin to your $PATH.

To compile the provider, run make build. This will build the provider and put the provider binary in the $GOPATH/bin directory.

$ make bin
...
$ $GOPATH/bin/terraform-provider-vcd
...

In order to test the provider, you can simply run make test.

$ make test

In order to run the full suite of Acceptance tests, run make testacc.

Note: Acceptance tests create real resources, and often cost money to run.

$ make testacc

The acceptance tests will run against your own vCloud Air setup, using the enviroment variables you should have set below:

export VCD_USER=***********
export VCD_PASSWORD=************
export VCD_ORG=**********
export VCD_EXTERNAL_IP=xxx.xxx.xxx.xxx
export VCD_URL=https://api.vcd.xxxxxxxx.xxxxxxxx.com/api
export VCD_EDGE_GATEWAY=xxxxxxxxx
export VCD_VDC="xxxxxxxx"

Pulling in the 'Go vCloud Air' (govcloudair) Library

If you've also been adding in functionality to the govcloudair library, you need to ensure your changes have been merged and then run:

$ make fetchvendor

This will pull in the latest version, including your changes, and you will be able to develop against the updated library.