Validor streamlines azure terraform module testing by automatically applying and destroying resources, ensuring efficient and reliable validation.
Terraform modules can fail in production due to untested configurations, provider incompatibilities, or incomplete setups.
Manual testing is time-consuming and error-prone.
Validor helps you:
Test modules in isolated environments before production.
Validate apply/destroy cycles with real provider interactions.
Run multiple modules concurrently for faster CI/CD pipelines.
Test with local sources, exceptions, and custom configurations.
Automate testing across teams and large codebases.
go get github.com/dkooll/validor
See the examples/ directory for sample Terraform modules and test configurations.
Run tests from the tests/ directory:
Module Testing
Executes full Terraform apply/destroy cycles for real validation.
Supports parallel and sequential execution modes.
Handles local source testing for module development.
Provides detailed error reporting with actionable feedback.
Flexible Configuration
Command-line flags for runtime configuration (-example, -exception, -local, -namespace).
Environment variable support for CI/CD integration.
Exception lists to skip problematic modules.
Configurable namespace for custom registry sources.
Advanced Terraform Support
Works with all major cloud providers and custom modules.
Respects Terraform state and resource dependencies.
Handles complex module structures and submodules.
Automatic cleanup of generated files and states.
Error Reporting & Logging
Structured error types for better debugging.
Outputstest summaries with failure details.
Integration with Go testing framework for CI/CD.
Command-Line Flags
-example: Comma-separated list of specific examples to test.
-exception: Comma-separated list of examples to exclude.
-local: Use local source paths instead of registry.
-namespace: Terraform registry namespace (default: "cloudnationhq").
-skip-destroy: Skip destroy operations after apply.
Environment Variables
For CI/CD pipelines, configure via environment variables:
VALIDOR_EXAMPLE: Specific examples to test.
VALIDOR_EXCEPTION: Examples to exclude.
VALIDOR_LOCAL: Enable local source testing (true/false).
VALIDOR_NAMESPACE: Registry namespace.
VALIDOR_SKIP_DESTROY: Skip destroy (true/false).
Local testing requires the module repository to be properly structured.
Namespace configuration allows testing against custom registries.
We welcome contributions from the community! Whether it's reporting a bug, suggesting a new feature, or submitting a pull request, your input is highly valued.