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>
Dagger
Dagger is a programmable deployment system.
Using Dagger, software builders can automate the deployment of any application to any infrastructure, in just a few lines of code.
The Dagger platform adapts to your application, not the other way around. Thanks to its ecosystem of reusable packages and flexible scripting system, Dagger can be dropped into any software project without requiring changes to its architecture or workflow. Think of it as your "devops superglu".
No matter how your deployment works under the hood, you can manage it with the same Dagger user interface. This makes developers more productive, because they don't have to learn a new workflow every time their deployment system changes.
Learn More
Download and Install
- Install Dagger from source
- Binary distributions [coming soon]
Community
Join the Dagger community chatroom on Discord. We welcome beginners and experts alike!
Alpha disclaimer
Dagger is alpha-quality software. It has many bugs, the user interface is minimal, and it may change in incompatible ways at any time. If you are still willing to try it, thank you! We appreciate your help and encourage you to ask questions and report issues.