#Standard input and `dagger call`
1 messages · Page 1 of 1 (latest)
No. What’s the use case, beyond not passing the value as an argument to the function?
All right, thanks, good to know 
I'm just playing around creating a module for Fabric where the use case is often to pipe something like pbpaste into it. But I suppose it's possible to make it work with an argument as well.
when it comes to piping, i think the use-case works only when directly sending a raw graphql query
not to confuse anything, but i think thats one case where piping makes sense. 😵💫
e.g
'{
container {
from(address: "your.private.registry/dotnet/sdk:8.0") {
withExec(args: ["dotnet", "-h"]) {
stdout
}
}
}
}' | dagger query --progress=plain