.png%3Falt%3Dmedia%26token%3Df1ea80d6-51a3-4edb-bfba-3349a6b8cf8f)
.png%3Falt%3Dmedia%26token%3Df1ea80d6-51a3-4edb-bfba-3349a6b8cf8f)
🏢Organization management
🛠️Config Management
GitHub Actions
How to use the CloudTruth configure-action
This walkthrough shows you how to use CloudTruth parameters safely and securely with GitHub Actions using our configure-action.
Prerequisites
Update GitHub Repository Secrets
Adding your CloudTruth API access token as a GitHub secret allows GitHub Actions to reference the API token when running a workflow. This allows you to bring configuration and secrets from your CloudTruth projects into GitHub workflows.
In your GitHub repository settings, add a new repository secret with the name
CLOUDTRUTH_TOKEN that contains your API access token as the value:
Adding a Repository Secret
The action can be used to inject the configuration and secrets from a project's environment into your GitHub workflow. Within the same job, steps following the action will have environment variables set to those in your project, based on the environment you choose:
1
---
2
name: 'demo'
3
on:
4
pull_request: {}
5
6
jobs:
7
demo:
8
runs-on: ubuntu-latest
9
steps:
10
- uses: cloudtruth/configure-[email protected]
11
with:
12
apikey: "${{ secrets.CLOUDTRUTH_TOKEN }}"
13
project: MyFirstProject
14
environment: default
15
16
- name: dump the environment
17
run: |
18
printenv | sort
Copied!
GitHub Action results will show the environment variables that were added to the job, and which parameters were redacted.
The output below comes from the configure-action repository and shows a run from parameters that were pre-configured for the configure-action demo script - your output will match the parameters you created.
.png?alt=media)
Example workflow result
Last modified 2mo ago