-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
🪟 🐛 Fix custom connection creation endpoint #19702
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code LGTM in accordance what we've discussed and outlined as a plan. Did not test locally, since the BE fix isn't in yet, so I'd anyway expect weird behavior still.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So the backend needs an update to correctly handle custom vs not? Because this looks like we're always creating custom now which was the issue before.
@krishnaglick the issue before was actually only related to updating: non-custom connectors need to be updated with Custom connectors should always be created with |
My confusion stems from |
Yes exactly - creating a connector via the UI is now always a "custom" connector which is scoped to the current workspace. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have not tested locally, but code looks good.
Closes #19637 PR that introduced this bug was a precision revert of another issue: #19627 This PR removes the createSourceDefinition() and createDestinationDefinition() methods in favor of the new createCustomSourceDefinition() and createCustomDestinationDefinition() methods. createSourceDefinition() and createDestinationDefinition() are to be deprecated. This PR does not address updating custom connectors. There is a backend issue for fixing this behavior here: #19669
* master: (74 commits) Fix support icon in sidebar fix: add BuildPulse report for helm ac tests (#19785) fix: yaml syntax (#19775) 🪟 🐛 Fix custom connection creation endpoint (#19702) Source facebook marketing: check "breakdowns" combinations (#19645) fix typo: notify instead of sync (#19737) find_non_rate_limited_PAT (#19736) Source Google Ads: fix schema for "campaigns" stream (#19700) 🎉 Source Asana: migrate to new SAT, added base HTTP errors handling (#19561) fix order not to randomly fail backward compatibility check (#19377) Bump helm chart version reference to 0.42.0 (#19706) fix: add extraEnv block (#19703) Bump Airbyte version from 0.40.21 to 0.40.22 (#19687) Bump helm chart version reference to 0.41.3 (#19685) Add connector builder server to airbyte proxy, kube overlays, and helm charts (#19554) dbt Cloud integration doc (#19619) 🪟 🎉 Display service token validation errors in the UI (#19578) 17644 Update Destination data type test to use the new data types (#19281) Docs: fix broken connector builder UI docs links (#19631) Bump Airbyte version from 0.40.20 to 0.40.21 (#19634) ...
What
Closes #19637
PR that introduced this bug was a precision revert of another issue: #19627
This PR removes the
createSourceDefinition()
andcreateDestinationDefinition()
methods in favor of the newcreateCustomSourceDefinition()
andcreateCustomDestinationDefinition()
methods.createSourceDefinition()
andcreateDestinationDefinition()
are to be deprecated.This PR does not address updating custom connectors. There is a backend issue for fixing this behavior here: #19669