Secrets used in the CI / CD workflows

Add the secrets for GitHub Actions

Add a new actions secret to

• the repository or

• organisation

Add the secrets to run the workflow locally (act)

• Download the files and secrets.

• Optional: in case the secret should be saved to a file during running the workflow, use echo -n "STRING" | base64 to encode the value.

• Add the secrets to .act/build.secrets.

• Use the following notation:

  GCP_SA_CREDENTIALS='[KEY-FILE-FROM-PASSWORD-MANAGER]'
  ROOMLE_BUILD_PAT='[TOKEN-FROM-PASSWORD-MANAGER]'

Workflow secrets

GH_TOKEN

• Required to access the roomle-dev/ci-tools repo.

• Download the secret from [e-mail] SemanticRelease PAT

NPM_TOKEN

• Download the secret from [e-mail] GitHub Token

SLACK_WEBHOOK_URL

• Copy the secret from GH Actions Webhook@Slack 'github-actions'

SLACK_WEBHOOK_URL_LIVE

• Copy the secret from GH Actions Webhook@Slack 'Release'

VITE_DUMMY_USER and VITE_DUMMY_PASSWORD

• [e-mail] on live-db

GOOGLE_BUCKET_CREDENTIALS

• GH Actions GCP Bucket Dev SA Key