https://github.com/cloudtruth/configure-action
Securely deliver CloudTruth configuration and secrets into your GitHub Actions workflows.
https://github.com/cloudtruth/configure-action
actions cloudtruth configuration-by-environment configuration-management dotenv environment-variables git-secrets github-actions secrets-management
Last synced: about 2 months ago
JSON representation
Securely deliver CloudTruth configuration and secrets into your GitHub Actions workflows.
- Host: GitHub
- URL: https://github.com/cloudtruth/configure-action
- Owner: cloudtruth
- License: apache-2.0
- Created: 2021-05-09T00:40:03.000Z (almost 5 years ago)
- Default Branch: main
- Last Pushed: 2025-04-08T10:14:13.000Z (10 months ago)
- Last Synced: 2025-10-22T20:45:51.683Z (4 months ago)
- Topics: actions, cloudtruth, configuration-by-environment, configuration-management, dotenv, environment-variables, git-secrets, github-actions, secrets-management
- Language: TypeScript
- Homepage:
- Size: 1.94 MB
- Stars: 6
- Watchers: 5
- Forks: 1
- Open Issues: 8
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
- Security: SECURITY.md
Awesome Lists containing this project
README
# configure-action

[](https://codecov.io/gh/cloudtruth/configure-action)
[](https://github.com/cloudtruth/configure-action/issues)
[](https://github.com/prettier/prettier)
[](https://opensource.org/licenses/Apache-2.0)
[](https://www.cloudtruth.com/)
CloudTruth centralizes your configuration and secrets information to make it easier
to manage.
This action allows you to extract the configuration and secrets from a project, scoped
to an environment, into your GitHub Actions workflow. This is done securely by ensuring
that the GitHub workflow engine is told which of your configuration values are considered
secrets, so it can ensure they are properly redacted. This is analogous to the behavior
you would see if you added your secrets directly to your GitHub organization or repository
and then accessed those secrets through the `secrets` object in your action.
This action will modify your `env` object to have values for all the parameters that
you have stored in your project for the given environment.
## Prerequisites
You must have an api key established in your CloudTruth account.
## Action inputs
| name | required | description |
| ---- | -------- | ----------- |
| `apikey` | `yes` | The CloudTruth Service Account API Key to use. |
| `project` | `yes` | The CloudTruth project (name or id) within the organization. |
| `environment` | `yes` | The CloudTruth environment (name or id) view to use. |
| `tag` | `no` | The CloudTruth tag (name) within the environment to use. If not specified, current values will be retrieved. |
| `overwrite` | `no` | (default: false) Allow existing environment variables to be overwritten. |
| `server` | `no` | (default: `https://api.cloudtruth.io`) The CloudTruth server to execute the query against. |
## Usage
Add a step to your workflow, ensuring that your CloudTruth service account api key is
stored in GitHub as a secret:
```yaml
- uses: cloudtruth/configure-action@v2
with:
apikey: "${{ secrets.CLOUDTRUTH_API_KEY }}"
project: ""
environment: ""
```
We recommend using tags to provide consistent retrieval of configuration.
Tags isolate your deployments from changes being made in real-time by users.
See our [GitHub Actions workflow](https://github.com/cloudtruth/configure-action/blob/main/.github/workflows/demo.yml)
for a working example.