692bd72095
HACK: the way buildkit works, we can only supply an Auth Provider for the entirety of the build session (`dagger up`). Therefore, we start by scanning all auth in the entire Cue tree and supply an auth provider for all of them. Drawbacks: - As soon as you add `auth` in a Pipeline for a registry, all other Pipelines have access to the same registry - You can't use different credentials for the same registry Fixes #301 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 --cwd install
# Run all tests
yarn --cwd 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