refactor: Remove authSpecification from Airbyte protocol #39
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lmossman
changed the title
lmossman
changed the title
sherifnada
approved these changes
Jul 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Relates to airbytehq/airbyte#15019
Protocol Change Proposal doc
Removes authSpecification from the Airbyte protocol, as it has been replaced by advancedAuth.
This should only be merged once all connectors in the Airbyte catalog have been migrated to advancedAuth and all references to
authSpecificationhave been removed from the Airbyte platform. See the epic for the status of the connector migrations.EDIT: All connectors have now been migrated off of authSpecification, and all references have been removed from the Airbyte platform, so this should now be safe to merge.
Note for users
Airbyte users and custom connector authors shouldn't need to worry about this change, since
authSpecificationis an internal-only field that requires changes to the Airbyte platform to function, so it should not be used by custom connectors or community members.The main consequence that users may see is if they upgrade their Airbyte platform to a version in which
authSpecificationis removed, but they are using an old version of a connector that still utilizesauthSpecification, then they may see an error message in the Airbyte UI when trying to open the connector settings, which will direct them to upgrade to the latest connector version to resolve the issue.