To which we say: you’re absolutely right. And if you’ve built anything serverless, you might have noticed that deploying with the Serverless Framework is a lot like running Terraform. If info is selected, only summary information will be shown, for debug, there will be some debug information and for trace the whole requests and responses will be shown.If your organisation uses automation to manage cloud infrastructure, you’ve almost certainly heard about Terraform. It will be added to the call as an environment variable AWS_SESSION_TOKEN. They will be added to the command call as envronment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.ĪWS Session Token to use in the authentication (if needed). In order to use AWS driver, your Terraform playbook should contain aws block.ĪWS Client ID and Secret Key to authorize the Terraform call. Mechanism to provide an authentication data into the Terraform command call. If this workspace does not exist, it will be created.

Terraform will switch to this workspace before any applicable action. If it is not set, default workspace will be used. Workspace of terraform to be used during terraform operations. These variables will be written to a temporary file and will be passed to Terraform using the -var-file= option.

If you are using resource files that reference external variables, set these variables here. This file will be passed to Terraform using -var-file= option. Could be one of: none, new file, existing file.Ībsolute path to Terraform var file.

If not set, commander workspace will be used. Working Directory where commands will be executed. Configuration procedure parameters ParameterĬommand that will be used as terraform client, like /usr/bin/terraform or /my/custom-terraform, or sudo terraform, etc.

Terraform plugins docs