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-cli-prerequisites.sh
bash
# Validates all required CLI tools are installed ./scripts/validate-cli-prerequisites.sh
validate-config.sh
bash
# Validates configuration files ./scripts/validate-config.sh --environment <env>
validate-deployment.sh
bash
# Validates deployment status ./scripts/validate-deployment.sh --environment <env>
validate-naming.sh
bash
# Validates Azure resource naming conventions ./scripts/validate-naming.sh --resource-group <rg>
validate-agents.sh
bash
# Validates agent configuration files ./scripts/validate-agents.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: @validation, @devops, @sre