You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We know we want something with this shape (control plane syncing its view of tasks with data plane), but I think the specifics depend upon how taskprov materializes in our deployments. Still, the Janus tasks table might already be stable enough that we can make progress here.
What is the justification for this? Right now, I think all of our taskprov-enabled deployments do not require a control plane. Has that changed, are we hoping to use the control plane for ourselves, something else?
I don't think we know enough right now to make good decisions about what to do here. I think it's possible that in a taskprov setting, partner aggregators will still want some observability into and possibly automated management of tasks, and I think divviup-api would be a reasonable place to wire that up. However it occurs to me that I have made the mistake of overloading this issue, which had the well-defined goal of reconciling tasks, with nebulous concerns informed by unclear requirements. So we should probably refocus this issue on task sync/reconciliation, and write up new issues as and when requirements come into focus.
No description provided.
The text was updated successfully, but these errors were encountered: