OCT-1825: Initial passthrough FastAPI server

[adam-gf]

Description

Definition of Done

1. Acceptance criteria are met.
2. PR is manually tested before the merge by developer(s).
   • Happy path is manually checked.
3. PR is manually tested by QA when their assistance is required (1).
   • Octant Areas & Test Cases are checked for impact and updated if required (2).
4. Unit tests are added unless there is a reason to omit them.
5. Automated tests are added when required.
6. The code is merged.
7. Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files).
   • BE: Swagger documentation is updated.
8. When required by QA:
   • Deployed to the relevant environment.
   • Passed system tests.

---

(1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required.

(2) Octant Areas & Test Cases.

[0xartem]

I looked at the code. it all looks good to me without going much into the details. I never worked with Fast API.
Questions:

• did we re-write all the back-end requests via Fast API?
• how do we test the improvements during the testing? Perfomance etc.

[kgarbacinski]

In general - LGTM, have you also checked with Mati the corectness of functionality within Flask endpoints only (whether the middlewared views save correct data to the db etc.)?

[kgarbacinski]

LGTM as the first stage, let's focus on all remaining pains before getting started with another functionalities

[housekeeper-bot]

E2E job #11438762470 passed 🎉

[adam-gf]

Due to problems with rebasing et al. We simply moved changes to separate pr and merged that one: #525.
Closing as it's resolved