...
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 FlexDeploy Property Replacement is supported in this input. For example: var1=${{MY_PROPERTY}} If you wish to use instance qualified properties it should be separated with ":" var1=${{INSTANCE1:MY_PROPERTY}} |
Terraform Snippet |
| No | An optional terraform snippet to be run instead, or in addition to, any local tf files. The content of the snippet will be written to a file named 'flexdeploy.tf' for execution. |
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 |
Ignore Terraform State |
| No | Ignore Terraform State changes to create multiple instances of the same type. If a backend has been configured in the code, this input will be ignored Defaults to false |
Init Parameters |
| No | Init parameters to add. (Ex: -backend-config="") |
Additional Arguments |
| No | Pass additional arguments to the terraform command. Useful for resource targeting (Ex: -target="") |
Global Options |
| No | Pass Global options arguments to the terraform command. Global options to add (Ex: -chdir="DIR") (chdir=DIR) - Changes the working directory before executing the subcommand. |
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.
...