UI: Backend for UI (Epic)

[jhmarina]

What needs to be done

Develop a backend for the UI. It can be implemented using either Python or NodeJS. The UI will speak to this backend via REST which will in turn speak to the S3 service.

Why it needs to be done

Serving the UI from a webserver will avoid CORS issues. This implementation is expected to also resolve the issue of accepting the certificate.

Acceptance Criteria

• Backend for the UI is created and implemented in either Python or NodeJS.
• The backend should be able to maintain state.
• It should avoid CORS issues.
• Certificate acceptance issues should be avoided.

Tasks

• docs: write a design doc for the UI backend #400
• ui: add backend s3gw-ui#165
• UI/Backend: SSL support #591
• UI/Backend: Containerize #592
• UI/Backend: Expose API endpoints required by the UI (Epic) #593
• UI: Make use of the REST API #680
• charts: Remove ingresses that were used because of CORS #720
• [FR] s3gw-ui: allow specifying custom certificate authorities (CA) for self-signed certificates #740

[jhmarina]

@jecluis will add tasks to this Epic once he evaluates the work that needs to be done.

[giubacc]

Since this Epic is assigned to 3 persons; it could be not obvious what is the expected effort from everyone (at least it is not obvious for me).
Should we make a plan? Should we divide the implementation of APIs across ourselves ?

[jecluis]

Jesus and I have spoken about this. We first need to make sure issues are filed, and then we'll figure this out in the coming days.

If you are aware of things that might be needed, please file issues for them. Same goes to you @votdev -- you probably know better what the backend should be delivering to the UI :)

[giubacc]

roger 👍

[giubacc]

is it ok I take https://github.com/aquarist-labs/s3gw/issues/592 ?
(asking because not sure if anyone already working on this)

[jecluis]

is it ok I take #592 ? (asking because not sure if anyone already working on this)

Sounds good!