AWS-specific
Setting up DynamoDB Access for locks
Getting Started
Features
How To
- 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
- 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
AWS-specific
Setting up DynamoDB Access for locks
Digger runs without a backend but uses a DynamoDB table to keep track of all the locks that are necessary for locking PR projects. On the first run in your AWS account digger checks for the presence of DiggerDynamoDBLockTable
and it requires the following policy for the DynamoDB access:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "ListAndDescribe",
"Effect": "Allow",
"Action": [
"dynamodb:List*",
"dynamodb:DescribeReservedCapacity*",
"dynamodb:DescribeLimits",
"dynamodb:DescribeTimeToLive"
],
"Resource": "*"
},
{
"Sid": "SpecificTable",
"Effect": "Allow",
"Action": [
"dynamodb:BatchGet*",
"dynamodb:DescribeStream",
"dynamodb:DescribeTable",
"dynamodb:Get*",
"dynamodb:Query",
"dynamodb:Scan",
"dynamodb:BatchWrite*",
"dynamodb:CreateTable",
"dynamodb:Delete*",
"dynamodb:Update*",
"dynamodb:PutItem"
],
"Resource": "arn:aws:dynamodb:*:*:table/DiggerDynamoDBLockTable"
}
]
}