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>
Dagger
Dagger is a portable devkit for CICD.
Using Dagger, software teams can develop powerful CICD pipelines with minimal effort, then run them anywhere. Benefits include:
- Unify dev and CI environments. Write your pipeline once, Dagger will run it the same everywhere.
- Reduce CI lock-in. No more re-writing everything from scratch every 6 months.
How does it work?
- Automate actions with your favorite programming language. No proprietary SDK: just regular shell, Go, Javascript, Python...
- Reuse actions from a large and growing catalog.
- Tie it all together in CUE - a revolutionary declarative language invented at Google. No more YAML hell!
- Test and debug instantly on your local machine. No more waiting 10min to catch a typo.
- Run your pipelines on any Docker-compatible runtime, for maximum portability. This means most modern CI runners can run Dagger out of the box.