[dagster-fivetran] Remove OpExecutionContext support in FivetranWorkspace.sync_and_poll #26585
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
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Dec 19, 2024
OwenKephart
approved these changes
Dec 20, 2024
…pace.sync_and_poll
maximearmstrong
force-pushed
the
maxime/remove-opexecutioncontext-fivetran-workspace
branch
from
a2848ca to
825f11f
Compare
maximearmstrong
deleted the
maxime/remove-opexecutioncontext-fivetran-workspace
branch
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.
Summary & Motivation
Following this discussion for Airbyte Cloud -
FivetranWorkspace.sync_and_pollshould only accept context of typeAssetExecutionContext.How I Tested These Changes
Same tests with BK