Deploy your infrastructure via a CircleCI pipeline using the Terraform orb. Integrate Infrastructure-as-Code (IaC) to help provision and manage any cloud, infrastructure, or service of your choice.
Is your feature request related to a problem? Please describe.
When trying to use a dynamic value with a plan or apply job, it is very difficult to pass the dynamically created value as a var or a var_file.
Describe the solution you'd like
The var_file attribute should accept an absolute path instead of expecting a var file from within the module path.
Describe alternatives you've considered
I've tried passing a variable directly, with the var attribute, but it does not seem that the plan/apply reads from environment variables set in a pre-step step.
Additional context
Here's my current setup, please let me know if there's a better way to do this:
The pre-step command, grabbing a variable created in another job:
Is your feature request related to a problem? Please describe. When trying to use a dynamic value with a plan or apply job, it is very difficult to pass the dynamically created value as a var or a var_file.
Describe the solution you'd like The var_file attribute should accept an absolute path instead of expecting a var file from within the module path.
Describe alternatives you've considered I've tried passing a variable directly, with the var attribute, but it does not seem that the plan/apply reads from environment variables set in a pre-step step.
Additional context Here's my current setup, please let me know if there's a better way to do this:
The pre-step command, grabbing a variable created in another job:
and the plan job:
I have tried unsuccessfully with the pre-step command, grabbing a variable created in another job and creating a new variable:
and the plan job:
but it seems $BASH_ENV is not loaded as $VERSION is empty.