From a98c86185bc0dfc4cc97298bcfb1d8a2cab4760b Mon Sep 17 00:00:00 2001 From: Jonathan Visser Date: Wed, 4 Dec 2024 13:04:27 +0100 Subject: [PATCH] docs: hypernode-deploy: Clarify parameters to be base64 encoded --- docs/hypernode-deploy/getting-started/configure-ci-cd.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/hypernode-deploy/getting-started/configure-ci-cd.md b/docs/hypernode-deploy/getting-started/configure-ci-cd.md index c36e2b36..75eb7f19 100644 --- a/docs/hypernode-deploy/getting-started/configure-ci-cd.md +++ b/docs/hypernode-deploy/getting-started/configure-ci-cd.md @@ -17,8 +17,8 @@ In this example we'll be covering the Github Actions CI/CD configuration. Hypernode Deploy needs a few 'credentials' to be able to function. The necessary credentials are: -1. The private SSH key. (`SSH_PRIVATE_KEY`) -1. The composer auth.json file, optional. (`DEPLOY_COMPOSER_AUTH`) +1. The private SSH key as base64 encoded string. (`SSH_PRIVATE_KEY`) +1. The composer auth.json file as base64 encoded string, optional. (`DEPLOY_COMPOSER_AUTH`) - This is only necessary when your project needs to access private Composer repositories. 1. The Hypernode API token, optional. (`HYPERNODE_API_TOKEN`) - This is only necessary when you make use of Hypernode API driven features like Brancher.