Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Connection update calls to use PATCH endpoint #15607

Closed
Tracked by #14174
teallarson opened this issue Aug 12, 2022 · 2 comments · Fixed by #16748
Closed
Tracked by #14174

Migrate Connection update calls to use PATCH endpoint #15607

teallarson opened this issue Aug 12, 2022 · 2 comments · Fixed by #16748
Assignees
Labels
area/frontend Related to the Airbyte webapp team/platform-move

Comments

@teallarson
Copy link
Contributor

teallarson commented Aug 12, 2022

Currently, we send the entire connection object including the entire syncCatalog on our Update calls. Once we are able to use PATCH calls, we should only send the minimum needed information to identify and update the record.

This will be coordinated with the Platform team implementing the new API endpoint. Create calls will continue to use POST.

@teallarson teallarson added the area/frontend Related to the Airbyte webapp label Aug 12, 2022
@octavia-squidington-iii
Copy link
Collaborator

cc @airbytehq/frontend

@teallarson teallarson changed the title Migrate Connection calls to use PATCH endpoints Migrate Connection update calls to use PATCH endpoint Aug 12, 2022
@krishnaglick krishnaglick self-assigned this Sep 28, 2022
@krishnaglick
Copy link
Contributor

This can be bundled into the connection form refactor work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/frontend Related to the Airbyte webapp team/platform-move
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants