a5e9ac8a0f
Code convention: use nouns instead of verbs whenever possible. Reasoning: One can apply just about anything to Kubernetes via this: deployment, load balancer, RBAC policy, a custom CRD resource, etc. Upstream those are called resources: You give `kubectl apply` one or more manifests and it will create the corresponding resources. Signed-off-by: Andrea Luzzardi <aluzzardi@gmail.com> |
||
|---|---|---|
| .. | ||
| cli | ||
| compute | ||
| examples/react/.dagger/env/default | ||
| 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