Thank you for your interest in contributing to CodeFlow Infrastructure! This document provides guidelines for infrastructure as code contributions.
- Fork the repository on GitHub
- Clone your fork locally
- Set up development environment:
- Azure CLI installed and configured
- Bicep CLI installed (optional)
- Terraform installed (if contributing Terraform)
- Create a branch for your changes
- Azure CLI
- Bicep CLI (optional, for Bicep templates)
- Terraform (for Terraform contributions)
- PowerShell or Bash
Bicep Templates:
# Validate Bicep file
az bicep build --file bicep/main.bicep
# Validate all templates
find bicep -name "*.bicep" -exec az bicep build --file {} \;Terraform:
# Format
terraform fmt -recursive
# Validate
terraform init
terraform validate- Follow Bicep best practices
- Use consistent naming conventions
- Add comments for complex logic
- Validate all templates before committing
- Validate all templates before submitting
- Update documentation as needed
- Test in a development environment (if possible)
- Create a pull request with a clear description
- All Bicep/Terraform templates validated
- Documentation updated
- No hardcoded secrets or credentials
- Resource naming follows conventions
- Tested in development environment (if applicable)
Follow Conventional Commits:
feat(infra): add Redis cache to Bicep template
Add Azure Cache for Redis to main.bicep.
Configure SSL and password authentication.
Closes #123
Use GitHub Issues with:
- Clear description
- Affected template/file
- Expected vs actual behavior
- Azure subscription details (if applicable)
- Error messages or logs
- GitHub Discussions: For questions
- GitHub Issues: For bugs and features
- See main CONTRIBUTING guide for more details
Thank you for contributing! 🎉