#Standard input and `dagger call`

1 messages · Page 1 of 1 (latest)

rain knot
#

Is it possible to do echo hello | dagger call some-function and access that data somehow?

cerulean ivy
#

No. What’s the use case, beyond not passing the value as an argument to the function?

rain knot
#

All right, thanks, good to know salute

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.

GitHub

fabric is an open-source framework for augmenting humans using AI. It provides a modular framework for solving specific problems using a crowdsourced set of AI prompts that can be used anywhere. - ...

elfin orchid
#

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