Runway will look in the root module directory for the tfvars file for an environment and if it is not present, it will return an error.
When you want to define your var files in another location, runway doesn't look to see if you specify a custom -var-file location and requires a placeholder file to be present. As you can see below both .tfvars are added to the command which is not necessary.
Bug Description
Runway will look in the root module directory for the tfvars file for an environment and if it is not present, it will return an error.
When you want to define your var files in another location, runway doesn't look to see if you specify a custom
-var-file
location and requires a placeholder file to be present. As you can see below both.tfvars
are added to the command which is not necessary.Also,
plan
does not even pick up the arg so it will not work at all with a custom.tfvars
location.Expected Behavior
It should not be required to have a
ENV.tfvars
file in the root directory if-var-file=
is specificed in theargs:
.apply
andplan
should have equivalent functionality.Steps To Reproduce
Runway version
2.6.2
Installation Type
pypi (pip, pipenv, poetry, etc)
OS / Environment
macOS 12.4
3.8.13
1.2.3
Anything else?
No response