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

Configs database should auto update connector definitions #5678

Closed
tuliren opened this issue Aug 26, 2021 · 0 comments · Fixed by #5723
Closed

Configs database should auto update connector definitions #5678

tuliren opened this issue Aug 26, 2021 · 0 comments · Fixed by #5723
Assignees
Labels
priority/high High priority type/bug Something isn't working

Comments

@tuliren
Copy link
Contributor

tuliren commented Aug 26, 2021

Current Behavior

  • Currently the configs database will skip the seed loading step if the database has already been initialized.
  • This means that if there are new connectors in the seed, they won't be added to the database.
  • It was not a problem in the file system persistence, because all connector definitions were automatically available.
  • In the database world, it is no longer automatic. We need to insert the connector record into the database.
  • Relates to UI is not getting new sources in setting page #5657.

Expected Behavior

  • When user upgrades to a new Airbyte version, new connector definitions should be available.
@tuliren tuliren added the type/bug Something isn't working label Aug 26, 2021
@tuliren tuliren self-assigned this Aug 26, 2021
@tuliren tuliren added the priority/high High priority label Aug 26, 2021
@tuliren tuliren added this to the Core 2021-09-01 milestone Aug 26, 2021
@tuliren tuliren changed the title Configs database should automatically pick up new connectors Configs database should auto update connector definitions Aug 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/high High priority type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant