feat(airbyte-ci): supports data activation flag in metadata service #59746
Conversation
This file contains hidden or 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
maxi297
commented
May 9, 2025
...tors/metadata_service/lib/metadata_service/models/src/ConnectorRegistrySourceDefinition.yaml
Show resolved
Hide resolved
bnchrch
reviewed
May 9, 2025
maxi297
changed the title
bnchrch
approved these changes
May 9, 2025
maxi297
changed the title
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
We're adding a new field to a connector's metadata for data activation. The field is already supported by the platform, and there's a destination connector (destination-cobra) that is using it in a merged PR which we will retrigger after we merge this
How
Add the field to the models and update the dependencies.
Review guide
User Impact
This should enable the flag to be populated in the platform
Can this PR be safely reverted and rolled back?