Skip to content

Commit

Permalink
Fix Vercel error caused by spaces before code snippet (#28408)
Browse files Browse the repository at this point in the history
  • Loading branch information
VioletHynes committed Sep 16, 2024
1 parent 7a5d99d commit c140470
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions website/content/docs/sync/github.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -35,11 +35,11 @@ Use `vault write` to configure a repository sync destination with an access toke
repository_owner="GITHUB_OWNER_NAME" \
repository_name="GITHUB_REPO_NAME"
```

For example:

<CodeBlockConfig hideClipboard>

```
$ vault write sys/sync/destinations/gh/hcrepo-sandbox \
access_token="github_pat_11ABC000000000000000000000DEF" \
Expand All @@ -64,11 +64,11 @@ Use `vault write` to configure a repository sync destination with an access toke
repository_name="GITHUB_REPO_NAME" \
environment_name="GITHUB_ENVIRONMENT_NAME"
```

For example:

<CodeBlockConfig hideClipboard>

```
$ vault write sys/sync/destinations/gh/hcrepo-sandbox \
access_token="github_pat_11ABC000000000000000000000DEF" \
Expand Down Expand Up @@ -177,7 +177,7 @@ depending on whether you have configured
If using the secret-path granularity, it is strongly advised to mask individual values for each sub-key to prevent the
unintended disclosure of secrets in any GitHub Action outputs. The following snippet illustrates how to mask each secret values:

```yaml
```yaml
name: Mask synced secret values

on:
Expand All @@ -192,7 +192,7 @@ unintended disclosure of secrets in any GitHub Action outputs. The following sni
for v in $(echo '${{ secrets.VAULT_KV_1234_MY_SECRET }}' | jq -r '.[]'); do
echo "::add-mask::$v"
done
```
```
If the GitHub destination uses the default `secret-key` granularity, the values are masked by GitHub automatically.

Expand Down

0 comments on commit c140470

Please sign in to comment.