868e96d06a
Adds the ability to select a template which will create a new file
in the CWD with the template name. Templates present in the
"cmd/dagger/project/templates" directory are automatically embedded in the dagger
binary when building and then listed in the `dagger project init` help output.
Usage:
dagger project init -t <template_name>
One idea that we had while pairing on this is to eventually try
improving this UX by extending the `dagger project` command by adding
sub-commands like `dagger project templates [list, new, output, ...]`.
Pair: gerhard
Signed-off-by: Marcos Lilljedahl <marcosnils@gmail.com>
|
||
|---|---|---|
| .. | ||
| cue.mod | ||
| plan | ||
| stdlib/terraform/s3 | ||
| tasks | ||
| age_key.txt | ||
| helpers.bash | ||
| package.json | ||
| plan.bats | ||
| project.bats | ||
| README.md | ||
| secrets_sops.yaml | ||
| tasks.bats | ||
| yarn.lock | ||
Testing
TL;DR
# Install dependencies
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
Run a single test
To run a single test:
make && ./tests/node_modules/.bin/bats "./tests/<TESTFILE>.bats" -f "<TESTNAME>"