Generated API Client

[krishnaglick]

Our service layer is now auto-generated from the OpenApi spec.

Closes #10181

[dizel852]

Extra "/" issue during creation of GitHub source

[dizel852]

Looks like one more issue:
I noticed that on the Sync History table we have short useful info (master branch):

But on this branch, they partially disappeared - Job type is gone, but "how many record" moved to JobLogs component:

Is it desired behavior? 🤔

[timroes]

Is it desired behavior? thinking

This is def not desired behavior and will look to get this fixed

[timroes]

Another bug: the logs view with multiple attempts should not be working atm, since the current code only pulls of the latest logs always. Going to look into that as well.

[timroes]

Tested the whole app thoroughly with this PR active. OSS as well as in Cloud. Looked at the code overall and the specific core files like apiOverride (have not reviewed the type only changes in every single file on detail). This looks as safe as we can get it before merging for me.

[dizel852]

I'm not sure if this issue relates to changes in this PR, but after the creation of a new connection, the sync job starts automatically(does it should?).
If we will try to cancel it, it will launch the sync again. So we are in the loop.
Was testing with different sources and dest - the same.
https://www.loom.com/share/8dae4109f7ff4e37ad8f41aeb1888d4b

Double-checked on stage env - didn't reproduce.
Wasn't unable to check this case on prod since I run out of credits

[timroes]

@dizel852 The start behavior is expected, that we immediately start a new job when creating a connection (and I verified it against prod). The repeating when cancelling the initial sync sounds weird (but also present on prod). I'll check with the other platform teams, because that does indeed look suspicious (but since both are present on prod, not a problem with this PR).

[dizel852]

@timroes ok, then.
No more issues were found.
Was testing locally (OSS)