#Container add `build` by vito · Pull Re...
1 messages · Page 1 of 1 (latest)
Is this how this feature should work?
query MyQuery {
git(url: "https://github.com/dagger/dagger") {
branch(name: "v0.2.x") {
tree {
id
}
}
}
}
container {
build(
context: "eyJsbGIiOnsiZGVmIjpbIkdxZ0JDaVZuYVhRNkx5OW5hWFJvZFdJdVkyOXRMMlJoWjJkbGNpOWtZV2RuWlhJamRqQXVNaTU0RWljS0ZHZHBkQzVoZFhSb2FHVmhaR1Z5YzJWamNtVjBFZzlIU1ZSZlFWVlVTRjlJUlVGRVJW..."
dockerfile: "Dockerfile"
) {
exec(args: ["version"]) {
stdout {
contents
}
}
}
}
}
looks like it
{
"data": {
"container": {
"build": {
"exec": {
"stdout": {
"contents": "dagger devel () linux/arm64\n"
}
}
}
}
}
}
but I was surprised that the dagger command was implicit
we loose some chaining compared to Directory { build } (you need to stitch 2 queries) but the latter form opened questions around extension points; do we support multiple kinds of build? Who decides available build backends? Is this how extenions will work in the future? etc
or maybe that's the ENTRYPOINT
probably sets ENTRYPOINT
didn't know these medal emojis existed, but they're perfect
especially the 2nd place
@modest coral I wouldn't know about that one. I heard it's nice but have never seen it
@tropic junco what was the name of my 1st grade teacher? I'm waiting...