#how will cloak API cutover happen?
past flare
Do we imagine the two being side by side as parts of the new API are incrementally merged?
Then we'll remove the old redundant bits?
past flare
yep current cloak -> what's being worked on
polar ore
yep, I'm not sure what things are leveraging the old API, but it's pretty painless to keep it around while we gradually move things over. we'll want it gone at some point though just so there's no confusion, since it was mostly a stepping stone
the queries don't overlap at all since the old API had everything namespaced under core { }
past flare
Awesome. Thinking about how we convert existing extensions using old core api and how we work with folks currently trying Cloak. Super helpful.
shy raven
Generally you can just focus on using what works today, and assume the transition will be easy
glass hound
Is cloak work actively being integrated in the current Dagger codebase already, or is the plan being built/prepared for now?
polar ore
it's actively developed in a branch at the moment: https://github.com/dagger/dagger/tree/cloak
glass hound
it's actively developed in a branch at the moment: https://github.com/dagger/dag...
Do you want to get the cloak branch in such a shape that it can run cue plans, then that branch becoming main?
polar ore
@worthy kite probably has a better answer
shy raven
& @sonic night for overall merge plan
worthy kite
Do you want to get the `cloak` branch in such a shape that it can run cue plans,...
Generally, the answer is yes. We're not totally solid on all of the mechanics yet.
But I am working on getting v0.2/Europa plans working on the cloak engine.
I'm still sorting through tracking it, but the beginnings are here: https://github.com/dagger/dagger/issues/3121
If there are specific things you're needing and wanting, let me know! Happy to hop on a video chat as well.