Skip to content

Commit 3dd080b

Browse files
authored
Merge pull request #1442 from diggerhq/feat/docs-gcp-bucket
Create using-gcp-bucket-for-locks.mdx
2 parents 3e62e59 + a0647e9 commit 3dd080b

File tree

3 files changed

+9
-2
lines changed

3 files changed

+9
-2
lines changed
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
title: "Using GCP bucket for locks"
3+
---
4+
5+
You can configure Digger to use a GCP bucket for locks. To do that, set the following setting in the workflow file:
6+
7+
- `google-lock-bucket` action input pointing to your bucket

docs/howto/using-terragrunt.mdx

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,6 @@ jobs:
7676
google-lock-bucket: please-create-me-for-storing-locks
7777
env:
7878
LOCK_PROVIDER: gcp
79-
GOOGLE_STORAGE_LOCK_BUCKET: please-create-me-for-storing-locks
8079
GOOGLE_ENCRYPTION_KEY: $\'{\'{ secrets.GOOGLE_ENCRYPTION_KEY \}\}
8180
GITHUB_CONTEXT: $\'{\'{ toJson(github) \}\}
8281
GITHUB_TOKEN: $\'{\'{ secrets.GITHUB_TOKEN \}\}

docs/mint.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,8 @@
129129
"group": "GCP-specific",
130130
"pages": [
131131
"gcp/setting-up-gcp-+-gh-actions",
132-
"gcp/federated-oidc-access"
132+
"gcp/federated-oidc-access",
133+
"gcp/using-gcp-bucket-for-locks",
133134
]
134135
},
135136
{

0 commit comments

Comments
 (0)