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

include webhook configs in operations db persistence layer #18030

Merged
merged 2 commits into from
Oct 16, 2022

Conversation

mfsiega-airbyte
Copy link
Contributor

What

Make sure the webhook configs are included in the db persistence layer.

This was missing from #17984, preventing the new operation type from actually being used.

Copy link
Contributor

@davinchia davinchia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch.

I think we should edit https://github.com/airbytehq/airbyte/blob/master/airbyte-config/config-persistence/src/test/java/io/airbyte/config/persistence/MockData.java#L402 to have a webhook test case as well.

This would have caught this in the previous PR.

Copy link
Contributor

@davinchia davinchia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty straightforward so feel free to merge after we have this.

@mfsiega-airbyte mfsiega-airbyte temporarily deployed to more-secrets October 15, 2022 23:38 Inactive
@mfsiega-airbyte mfsiega-airbyte merged commit aa1372c into master Oct 16, 2022
@mfsiega-airbyte mfsiega-airbyte deleted the msiega/dbt-cloud-persist-operations branch October 16, 2022 00:46
jhammarstedt pushed a commit to jhammarstedt/airbyte that referenced this pull request Oct 31, 2022
…#18030)

* include webhook configs in operations db persistence layer

* add unit tests for operations persistence
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants