When to Use
- Pre-deployment validation
- Post-deployment verification
- Configuration compliance checks
- Naming convention validation
Prerequisites
- Bash shell
- Required CLI tools (az, kubectl, terraform, gh)
- Appropriate permissions for target resources
Available Scripts
validate-prerequisites.sh
# Validates all required CLI tools are installed
./scripts/validate-prerequisites.sh
validate-config.sh
# Validates configuration files
./scripts/validate-config.sh --environment <env>
validate-deployment.sh
# Validates deployment status
./scripts/validate-deployment.sh --environment <env>
validate-agents.sh
# Validates agent configuration files
./scripts/validate-agents.sh
validate-docs.sh
# Validates documentation files
./scripts/validate-docs.sh
Best Practices
- Run validation before any deployment
- Include validation in CI/CD pipelines
- Document validation failures clearly
- Exit with non-zero code on failure
- Provide remediation steps
Output Format
- Script executed
- Validation results (pass/fail)
- Details of any failures
- Remediation recommendations
Integration with Agents
Used by: @test, @devops, @sre
Converted and distributed by TomeVault — claim your Tome and manage your conversions.