Skip to content
This repository has been archived by the owner on Sep 16, 2020. It is now read-only.

Terraform Module Feature Validation Locally #105

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

xchapter7x
Copy link

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 :)

the desired behavior and intent should be
clearly defined. It should also be tested
to be true on a unit level.

this brings base coverage to the feature
expectations for pas, rds and control plane
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants