Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/linguinecode/codebuild-env-vars
https://github.com/linguinecode/codebuild-env-vars
Last synced: 22 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/linguinecode/codebuild-env-vars
- Owner: LinguineCode
- License: mit
- Created: 2019-01-30T01:24:45.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2019-02-01T17:22:20.000Z (almost 6 years ago)
- Last Synced: 2024-10-28T09:33:06.194Z (2 months ago)
- Language: Shell
- Size: 2.93 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# codebuild-env-vars
Echo back all environment variables listed in this document: https://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref-env-vars.html
## Usage
Add the following command to the `install` or `pre_build` phase of your buildspec:
```
bash -c "$(curl -fsSL https://raw.githubusercontent.com/solsglasses/codebuild-env-vars/master/install.sh)"
```
## Why not just `printenv | grep ^CODEBUILD`?
I want to see the value of all of these environment variables, even if they were not set. `printenv` will only print environment variables that are declared (obviously). In certain scenarios, especially when running [aws-codebuild-local](https://aws.amazon.com/blogs/devops/announcing-local-build-support-for-aws-codebuild/), many of these environment variables do not get set.