Hi folks
If I run TS_ENV=dev terraspace up eks-cluster --yes -lock-timeout=30m, I can clearly see from the terminal that this -lock-timeout argument is passed to the Terraform commands:
=> terraform plan -lock-timeout=30m -input=false
module.eks-cluster.data.aws_vpcs.vpcs: Reading...
module.eks-cluster.data.aws_ssm_parameter.custom_ami_image_id: Reading...
module.eks-cluster.data.aws_caller_identity.current: Reading...
When I run the same command with all up instead, the argument goes missing:
=> terraform plan -input=false
Acquiring state lock. This may take a few moments...
module.eks-cluster.data.aws_ssm_parameter.custom_ami_encryption_kms_key: Reading...
module.eks-cluster.data.aws_region.current: Reading...
module.eks-cluster.data.aws_caller_identity.current: Reading...
Is there a way to send additional Terraform arguments to the Terraspace all up command? It’s an important part of our pipeline to allow us to retry deployments when state locks are encountered.
Thanks in advance
Duncan