Infrastructure as Code Lifecycle
This guide explains how DeployStack manages and updates your Infrastructure as Code (IaC) templates throughout their lifecycle.
Template Generation Process
Initial Setup
- Create a .deploystack configuration directory in your repository
- Add your Docker configuration files:
docker-compose.yml for Compose configurations
docker-run.txt for Docker run commands - Submit your repository to deploystack.io/submit
- Initial IaC templates are generated and stored in our deploy-templates repository
Enabling Automatic Updates
Install the DeployStack Repository Sync GitHub App to keep your templates up to date when:
- You modify Docker configurations in the .deploystack directory
- Cloud providers update their IaC specifications
- DeployStack improves its template generation
Update Triggers
Your IaC templates are automatically updated in these scenarios:
Repository Changes
When you modify files in your repository's default branch:
- Changes to docker-compose.yml or docker-run.txt in .deploystack directory
- Updates to repository metadata
Provider Updates
Templates are regenerated when:
- Cloud providers modify their IaC specifications
- New provider features become available
- Provider API requirements change
System Updates
DeployStack initiates template updates when:
- The docker-to-iac module receives improvements
- New template optimizations are available
- Bug fixes are released
Template Versioning
All template updates are version controlled in our deploy-templates repository, allowing you to:
- Track template changes over time
- Review modification history
- Understand update triggers