Introduction
Getting Started
Digger Enterprise
Features
How To
- Managing state
- Specify terraform version
- Apply on Merge
- Apply Requirements
- Auto-merge
- Backendless mode
- Commenting strategies
- Custom commands
- Destroy via manual workflow
- Draft PRs
- Disable auto-checkout
- Disable telemetry
- Generate projects
- Group plans by source module
- Include / exclude patterns
- Masking sensitive values
- Multiple AWS accounts
- Policy overrides
- Project Level Roles for AWS
- Segregate cloud accounts
- Store plans in a Bucket
- Trigger workflow directly
- Using Checkov
- Using Infracost
- Inline policies (conftest)
- Using Terragrunt
- Specifying version
Self-host Digger
AWS-specific
Troubleshooting
GCP-specific
Using GCP bucket for locks
You can configure Digger to use a GCP bucket for locks. To do that, set the following setting in the workflow file:
google-lock-bucket
action input pointing to your bucket
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.