-
Notifications
You must be signed in to change notification settings - Fork 35
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
terraform module feature: pre-processing options #171
Comments
Yes! 🔥 |
hopefully have something for you soon. Still kinda working out what this would look like, and how to make it easy to use without having to be repeatable for all the targets. (might be a necesarry evil though). one additional thing I will add to this, or maybe as a separate thing on its own PR, is the ability to generate lockfiles for providers on other platforms (to support cross-platform dev teams, and combined CI/local workflows) |
I'm thinking of contributing some pre-processing options for the terraform executor. Basically, when using a monorepo, working directory and context become critical, and plan/apply times can skyrocket due to node_modules. Even ignoring these files doesn't stop them from being evaluated locally before the plan/apply executes.
a "preProcessing" options config would allow you to specify a directory to move the tf files to prior to running tf commands. This would allow you to use relative directories with modules so that they work in editors for syntax highlighting/completion/linting, but execute quickly for local and ci plan/apply because the context directories would be smaller.
Would you support a contribution for this type of feature?
The text was updated successfully, but these errors were encountered: