Scope lowcode UI v1 backend items

[sherifnada]

Acceptance Criteria

• A scoped list of the backend tickets required to power the v1 PRD requirements (https://docs.google.com/document/d/1gbZufczSsR2VuUw6z6oDn7iDmG7xt06_GiZ6wYrrmk4/edit#heading=h.agrxfsjj7zsy)

[sherifnada]

only two issues we can think of atm:

• only returning specific pages/slices
• Get alignment on if & how the openAPI spec evolves for v1

[sherifnada]

I reviewed the PRD v1 requirements. The issues I think we will need to support v1:

hard requirements

• [ ] Support for specifying stream schemas in the UI and sending it to the backend https://github.com/airbytehq/airbyte/issues/19499 The current frontrunner approach is bundling schema definitions into the manifest, but it doesn't have to be implemented that way.
• [ ] support limiting number of pages / records retrieved from connector builder server https://github.com/airbytehq/airbyte/issues/19500

later

• Support fetching a specific single page and/or slice, to allow users to test read page-by-page for better performance
• (eventually, likely not Q1) a CRUD API for connector-builder-built connectors, to support a UI where users can see and manage all of their built connectors
• Generate acceptance / snapshot tests for low-code connectors? (Though this may be unrelated to the connector builder UI)
• Auto-detecting schema, so that it can be displayed when testing the connector read

[sherifnada]

@lmossman I'd like to close this issue with the above comment. LMK if you have any feedback by thursday sprint planning please.

[lmossman]

@sherifnada I left a comment on #19500 but otherwise I think this looks good

[sherifnada]

responded there, thanks for the response!