Destroys resources created using previous apply operation, make sure to consistently use backend state or state directory.
...
...
Property Name
...
Property Code
...
Required
...
Description
...
Terraform Version
...
FDTF_TF_EXE_VERSION
...
No
...
Desired version of the terraform executable to be downloaded.
Defaults to version 0.12.24
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Cloud Accounts |
| No | FlexDeploy Cloud Accounts to use for authorization and connection. See the home page for more information on Cloud Accounts and configuring authorization. @since 6.5.0.8 , plugin supports only one Cloud Account. Multi select option is disabled. The provided account will be considered for resource deployment and backend state management both (if applicable). For example, deploying resources to AWS cloud, may require the backend state to be managed in s3 bucket. |
Variables |
| No | Terraform variables to use. Separate key value by '=' and put entries on separate lines. var1=val1 var2=val2 |
State Directory |
| No | Local directory where to maintain state. If using a backend state manager, then leave this blank. If blank and no backend is detected, this will default to the internal state directory for the project. /var/flexdeploy/terraformstate/%projectId% |
Terraform Path |
| No | If the Terraform executable is not on the path you can specify the location here |
Terraform Version |
| No | Desired version of the terraform executable to be downloaded. Defaults to version 0.12.24 |
Outputs
Allows user defined outputs. All outputs defined in the Terraform configuration are available to be returned as FlexDeploy outputs. Simply add them to the Outputs tab in the plugin configuration.
...