https://github.com/circleci/encrypted-files
Storing encrypted files in source on CircleCI
https://github.com/circleci/encrypted-files
Last synced: about 1 year ago
JSON representation
Storing encrypted files in source on CircleCI
- Host: GitHub
- URL: https://github.com/circleci/encrypted-files
- Owner: circleci
- Archived: true
- Created: 2016-07-20T18:55:54.000Z (almost 10 years ago)
- Default Branch: master
- Last Pushed: 2024-02-06T14:32:38.000Z (over 2 years ago)
- Last Synced: 2025-02-22T19:12:30.254Z (over 1 year ago)
- Homepage:
- Size: 3.91 KB
- Stars: 104
- Watchers: 54
- Forks: 21
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
- Codeowners: CODEOWNERS
Awesome Lists containing this project
README
# encrypted-files
This is a simple example of storing encrypted files in source for use in CircleCI builds.
In this example, the gitignored contents of `secret-env-plain` are:
```
export FOO=secret
export BAR=alsosecret
```
If they are encrypted with `openssl aes-256-cbc -e -in secret-env-plain -out secret-env-cipher -k $KEY`, and `$KEY` is set
in the CircleCI project, the variables in `secret-env-plain` will be available in the build.
You could use the same process but replace the `openssl` command in `circle.yml` with `openssl aes-256-cbc -d -in secret-file-cipher -out secret-file-plain -k $KEY` to create plaintext files in the build environment instead of just exporting environment variables.