Personally, I would only expose /api/v1 endpoints that are currently required to integrate gooseBit the surrounding infrastructure (like uploading software from a CI). This because /api/v1 should be a stable interface. The wider it is, the more likely we will break it.
In /ui/bff we have more freedom to change things around, so we also don't need the optimal structure right from the start but will find it over time.
As discussed here https://github.com/UpstreamDataInc/goosebit/pull/58#discussion_r1717919294, we wanted the UI to only call
/ui/bff- never/api/v1. Somehow I missed to this is not yet implemented, so creating a ticket for it here.Personally, I would only expose
/api/v1endpoints that are currently required to integrate gooseBit the surrounding infrastructure (like uploading software from a CI). This because/api/v1should be a stable interface. The wider it is, the more likely we will break it.In
/ui/bffwe have more freedom to change things around, so we also don't need the optimal structure right from the start but will find it over time.