From 32e7cc357a0fecb1d9a2bda96e2479b9993b6b47 Mon Sep 17 00:00:00 2001 From: unglaublicherdude Date: Wed, 19 Jun 2024 11:54:42 +0200 Subject: [PATCH] adds an example of how to generate the value you actually have to put into dockerconfigjson --- README.md | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index b7acd10..476c5f5 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,18 @@ global: imagePullSecrets: - registry secret: - dockerconfigjson: "BASE64_ENCODED_JSON_CONTAINING_TOKEN" + dockerconfigjson: "BASE64_ENCODED_JSON_CONTAINING_DOCKER_AUTH_CONFIG" +``` + +You can generate this value with a bash command like this +```bash +echo '{ + "auths": { + "ghcr.io": { + "auth": "TO_BE_REPLACED" + } + } +}' | sed "s/TO_BE_REPLACED/$(echo "username:token" | base64 -w 0 )/g" | base64 -w 0 ``` * Install Verdict-as-a-Service: @@ -172,7 +183,7 @@ In addition, Sentry will always behave as follows: | Parameter | Description | Value | -|-------------------------------------------|-------------------------------------------------------------------------------------------------------|--------------------------------| +| ----------------------------------------- | ----------------------------------------------------------------------------------------------------- | ------------------------------ | | global.imagePullSecrets | List of image pull secrets | - name: registry | | global.secret.dockerconfigjson | Docker authentication configuration | "" | | cloud.hashLookup.enabled | Enable/Disable the cloud hash lookup | true |