This repository has been archived by the owner on Sep 16, 2020. It is now read-only.
Terraform Module Feature Validation Locally #105
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I realize this is quite the out of left field PR, but I figured a PR would better speak to the approach than I could articulate in words. I'm curious on the teams thoughts.
This is an attempt at an approach that can help us to define "unit" behaviors and effectively TDD the modules.
We frequently modify the modules with clients and it is not immediately clear if there are side-effects or if the intended behaviors have been broken by our changes. The hope is this can bring some safety to client modifications, via tests as guard rails and guidance and greater visibility of intent.
Let me know thoughts on this approach. Thanks :)