9c0e2d1d95
- Secrets are never exposed in plaintext in the Cue tree. `dagger query` won't dump secrets anymore, Cue errors won't contain them either. - BuildKit-native secrets support through a new `mount` type. This ensures secrets will never be part of containerd layers, buildkit cache and generally speaking will never be saved to disk in plaintext. - Updated netlify as an example - Added tests - Changed the Cue definition of a secret to: ``` @dagger(secret) id: string } ``` This is to ensure both that setting the wrong input type on a secret (e.g. `dagger input text`) will fail, and attempting to misuse the secret (e.g. interpolating, passing as an env variable, etc) will also fail properly. Signed-off-by: Andrea Luzzardi <aluzzardi@gmail.com> |
||
|---|---|---|
| .. | ||
| cli | ||
| compute | ||
| examples/react | ||
| ops | ||
| stdlib | ||
| cli.bats | ||
| compute.bats | ||
| examples.bats | ||
| helpers.bash | ||
| ops.bats | ||
| package.json | ||
| README.md | ||
| stdlib.bats | ||
| yarn.lock | ||
Testing
TL;DR
# Install dependancies
yarn install
# Install gnu parallel if needed
# macOS
brew install parallel
# Debian derivatives
# apt-get install parallel
# Install sops if needed
# macOS
brew install sops
# Run all tests
yarn test
By default, the dagger binary is expected to be found in ../cmd/dagger/dagger relative to the tests directory.
If you need to change this, pass along DAGGER_BINARY=somewhere/dagger