-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Rename registries to registryOverrides in connector metadata #43757
Rename registries to registryOverrides in connector metadata #43757
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @alafanechere and the rest of your teammates on |
d1a6142
to
63fd362
Compare
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.
connector changes look legit (just find+replace)
just to doublecheck (I didn't read the previous PR in the stack) - are there any backwards-compat things to solve? I.e. will old connector metadata continue working, does anything need to be modified in platform, etc
@edgao the upstream PR should be merged first and will rename the fields where it's actually used for registry generation. This override logic happens at connector registry generation, so the platform is not aware of these fields.
|
8f0a6af
to
9521bfb
Compare
What
Rename
registries
toregistryOverrides
in connector metadata.yaml.Skipping CI to not trigger tests on all connectors
Manual testing on
destination-postgres
: https://github.com/airbytehq/airbyte/actions/runs/10353121102