diggerhq/digger
Digger
Digger is a GitOps infrastructure automation system and Terraform orchestrator. It enables the execution of infrastructure plans and applies directly from version control pull requests and CI pipelines.
The project provides a framework for policy-based governance and state management. It enforces role-based access controls and custom security policies on infrastructure changes, while centrally storing state files with version history and access controls.
The system manages infrastructure workflows through pull request comment triggers and remote execution. It includes capabilities for drift detection to identify discrepancies between actual and desired cloud states, concurrent execution locking to prevent race conditions, and plan persistence to ensure approved versions are applied to production.
Features
- Pull Request Comment Triggers - Enables the execution of infrastructure plans and applies directly via specific pull request comments.
- Orchestrators - Orchestrates Terraform plans and applies directly from version control pull requests and CI pipelines.
- Orchestration State Management - Provides centralized management of infrastructure state to coordinate cloud operations and maintain a single source of truth.
- State Management - Provides centralized storage for infrastructure state files with integrated access controls and version history.
- GitOps Automation - Triggers infrastructure updates and state changes directly based on activity within version control pull requests.
- GitOps Workflows - Synchronizes infrastructure state with version control using automated deployment pipelines triggered by pull requests.
- Infrastructure as Code Deployments - Manages the deployment and execution of infrastructure code through automated pipelines and remote environments.
- Infrastructure Automation Workflows - Automates the modification and deployment of infrastructure resources through integrated workflows.
- Infrastructure Governance Policies - Enforces automated rules and role-based access controls on infrastructure changes to ensure security and compliance.
- Infrastructure State Managers - Maintains infrastructure state files centrally with access controls and version history to ensure consistency.
- Infrastructure Policy Enforcers - Enforces security standards and custom compliance policies on infrastructure-as-code definitions before deployment.
- Policy-Based Access Control - Enforces security permissions and custom rules on infrastructure changes through a policy-driven authorization system.
- Drift Detection - Identifies discrepancies between the actual cloud resource states and the desired states defined in infrastructure-as-code configuration.
- Infrastructure Resource Locks - Implements locking mechanisms to prevent concurrent modifications to the same infrastructure project or workspace.
- PR Action Workflows - Provides interfaces for triggering common infrastructure actions such as plans and applies from a pull request view.
- Remote Workspace Command Execution - Provides the capability to execute shell commands and manage files on remote hosts via connected workspace instances.
- Drift Detection - Automates the identification of discrepancies between defined infrastructure code and the actual cloud environment state.
- Remote Worker Command Executors - Executes infrastructure shell commands on remote cloud worker instances and streams real-time logs back to the user.
- Race Condition Prevention - Prevents data races and concurrent modifications by using locks on pull requests during infrastructure updates.
- Plan Approval Workflows - Saves proposed infrastructure changes for human approval before execution to ensure safe production deployments.
- Plan Persistence - Caches execution plans in cloud storage to ensure the approved version is exactly what is applied to production.
Star history
How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.
