destroy
- Chandresh Patel
- Tristan Butzine (Unlicensed)
- Vivek Vanka
Destroys resources created using previous apply operation, make sure to consistently use backend state or state directory.Â
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Terraform 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. |
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 |
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.
Artifacts
This operation consumes artifacts from the artifacts repository.
Endpoint Selection
This operation will select all available endpoints associated to the Target.
Endpoint Execution
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.
Special Considerations
Terraform configuration files are expected to be in the FlexDeploy Artifact Repository
- style