Merge dagger.io/dagger/engine into dagger.io/dagger#1579
Merge dagger.io/dagger/engine into dagger.io/dagger#1579shykes merged 1 commit intodagger:mainfrom shykes:api-cosmetics
Conversation
|
✔️ Deploy Preview for devel-docs-dagger-io ready! 🔨 Explore the source changes: 1f362087762ee88a60bb759a8c1487abab2c3e11 🔍 Inspect the deploy log: https://app.netlify.com/sites/devel-docs-dagger-io/deploys/620c2de20939aa00074a2af4 😎 Browse the preview: https://deploy-preview-1579--devel-docs-dagger-io.netlify.app |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
TomChv
left a comment
There was a problem hiding this comment.
I understand why core types are move to dagger.io/dagger, that's easier to maintains and it feel more logical.
But I'm not sure about the name builtins, to more, #Exec.. are more like primitive action, I'm not sure that engine was the perfect name, but builtins feel strange to me.
I don't have a better proposal for now, just giving my feeling
Builtin actions
Import path: dagger.io/dagger/engine
It should be dagger.io/dagger/builtins no?
You also forget the git ignore in tests/core/secrets/simple/cue.mod
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
Should be good to go @aluzzardi |
|
Final touches:
|
Signed-off-by: Solomon Hykes <[email protected]>
|
Should be all good to go (for real now :) |
|
Good-bye, |
Overview
Merge
dagger.io/dagger/engineintodagger.io/dagger. The result is a single package known as the Dagger CUE API, version 0.2. It is documented below.Dagger CUE API (0.2+)
As of Dagger 0.2 (codename Europa), the Dagger CUE API can be imported at
dagger.io/dagger.The Dagger CUE API is the set of CUE packages released alongside the Dagger engine, to allow developers to access its features.
Plan definition
#Plandefines the structure of a Dagger plan - a complete configuration executable bydagger up.Core types
Dagger extends the CUE type system with the following core types:
#FS: a reference to a filesystem tree#Secret: a secure reference to an external secret#Servicea reference to a network service endpointsCore actions
Dagger works by executing actions in a certain order and passing data between actions in a certain layout.
Developers can combine actions into higher-level actions, which in turn can be combined into even higher-level actions,
and so on at arbitrary levels of depth. At the bottom of this abstraction stack are core actions: these
are implemented by Dagger itself, and are always available.
The following core actions are available:
#Exec#HTTPFetch#Push#Pull#Dockerfile#Set#GitPush#GitPull#DecodeSecret#NewSecret#Source#Mkdir#ReadFile#WriteFile#Scratch#Copy#Subdir