#So, I now have a client-based function
1 messages ยท Page 1 of 1 (latest)
So if you want dagger fully embedded in a program, you don't need to dagger run go run ., you can just go run .. You'll miss out on the nice TUI and maybe some other things I'm not thinking of, though
What is the TUI?
The nicely formatted output you get in the terminal with the dagger CLI. Without the CLI executing the pipeline, you'll get a raw format of output
So, let's say in my CI process, I want to offer logs to the dev like Circle CI does it, then I need the better output? ๐ค I guess I need to see what the raw output looks like.
The raw output looks similar to how it looks in circleci. But if you're running locally with the dagger CLI, you'll see output more like this
Hmmm.... we don't expect to have any devs sitting in front of terminals while CI tasks run though. They should be working on their next challenges. ๐ And, we also don't expect them to run Dagger functionsr for testing or other local development tasks either (I know, avoiding an advantage of Dagger). We can't as of yet, because we can't allow direct access to the Dagger engine, as these devs are third party to the k8s cluster, which the Dagger engine would be a part of.
Our dev environments are inside k8s too, if that wasn't clear. ๐
Ah understood, yes I was assuming that devs would be running pipelines locally. In that case, the TUI is not a factor either way
dagger run is a convenience that lets the end user control their dagger session. Enabling the interactive TUI is one example of such control. But it can also be used to connect to a remote engine, or hook up to your own Dagger Cloud account, etc.
But as Kyle said, it's always optional
Thanks. Let me run with this for now. I'm still having issues with Temporal I haven't yet figured out. But, once I do, then theoretically I'm finally off to the races... ๐
Can you point me to the relevant part of the temporal docs?
I wonder how easy it would be to wrap dagger call in there as a stopgap
Do you mean point to where I'm having issues with Temporal? Or how I intend to use Dagger in Temporal?
From what you are wondering, I would say the latter. ๐
I was planning to add Dagger to Activities. https://docs.temporal.io/dev-guide/go/foundations#activity-definition
My problem is though, I can't get the simplest of workflows to fire off (not even using an Activity yet). So, I have an issue with my Temporal installation, which I've not been able to troubleshoot much as of yet.
maybe you should daggerize your temporal test environment? ๐
dagger-in-temporal-in-dagger
Um..it would need to be more like dagger-in-k8s-in-temporal-in-dagger-in-k8s. ๐คฏ