-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the working directory configurable per command #81
Comments
We should consider using terraform's |
Need to have the mixin config accept multiple workingDirs as well:
|
Also need to figure out the case at the action level:
|
Logic to support this would need to be able to mutually exclusively set "workingDir" or "workingDirs" at the mixin level so that the terraform can be built into the bundle. And then require at the action level if "workingDirs" is set that each terraform action requires one of the values set in the mixin config. |
I recently added working directory as a mixin level config, which lets the user override the default directory with all their terraform files. #61 Sometimes people have multiple terraform modules though, and its not possible to use more than one in the same bundle. We should add working directory to the terraform mixin command so that you can do something like this:
The text was updated successfully, but these errors were encountered: