#wagon
limpid token
Only image config resolve need to hard-coded graphql https://github.com/octohelm/wagon/blob/main/pkg/engine/plan/task/core/image.go#L113-L163
Other flow task could be easy with new dagger client.
core.#Run & { always: true } hacked by https://github.com/octohelm/wagon/blob/main/pkg/engine/plan/task/container_run.go#L72-L75
And source cache issue, hacked by add time base exclude
https://github.com/octohelm/wagon/blob/main/pkg/engine/plan/task/fs_source.go#L48
Now, it works well in my projects.
Since the Pull & Push auth feature landed.
edgy gorge
impressive work! And a very appreciated contribution to the community
Would it make sense to make this the new official dagger-cue? Is it compatible enough in your opinion? And if so would you be up for being an official maintainer for it?
or maybe we do the opposite 😁
merge dagger-cue into wagon?
and advertise it to send users your way
limpid token
and advertise it to send users your way
From dagger-cue to wagon, may have to change something.
So it's not compatible enough.
Now I just make my old projects with dagger-cue works on new dagger engine.
I removed the ClientFilesystemWrites to avoid unnecessary copies and hacking cuelang.
And dagger.#Socket core.#Start/#Stop/#SendSignal, which not used in my case with k8s, I think i will not add it to wagon.
I think we could be let dagger-cue shutting down,
and provide utils to help cuelang user to build custom tool based-on cueflow.
edgy gorge
are you also building that? 🙂
limpid token
Not sure, I think we could do some refactor from dagger-cue and wagon both, and extract the common tools:
Maybe this https://github.com/octohelm/wagon/tree/main/pkg/engine/plan/internal
- TaskFactory, which register task written in golang.
- TaskRunner, which run cueflow with dagger engine.
Now all my tasks registered in this way https://github.com/octohelm/wagon/tree/main/pkg/engine/plan/task
cuelang decls will auto generated. https://github.com/octohelm/wagon/blob/main/pkg/engine/plan/internal/cueify.go