I see that `web_backend` api is very similar to co...
# contributing-to-airbyte
s
I see that
web_backend
api is very similar to connections but it adds some info, what's the purpose of this api?
u
It simplifies the implementation of the frontend
u
moves the logic of glueing the rest calls on the backend instead of the webapp
u
got it
u
can I rely on it?
u
nope
u
you should use the actual resource endpoints
u
how can I get the lastSync otherwise?
u
hum
u
go through the jobs?
u
let me check
u
I would say so, that's what we do in the webapp definition
u
Just concerned that in introduces a second definition now
u
I think we should expose this info in the primitive api, not in the web_backend one
u
is it a pb for you to go through the jobs right now?
u
I'll just use the web_backends for now
u
ok
u
knowingly that it will change
u
def a +1 for having that in the primitive api
u
also, i'd love if we can create/delete workspaces
u
that would solve most of my issues when segmentating multiple users in the same instance
u
I created this issue to enable it
u
Thank you 🙏
u
we already support it internally but we aren't exposing it
u
it will mostly be UI work
u
(and the API mgmt)
u
we don't need UI, only the api
u
added comment