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

chore(data-warehouse): Add a reset pipeline input to the external data job workflow #27881

Merged
merged 1 commit into from
Jan 24, 2025

Conversation

Gilbert09
Copy link
Member

Problem

  • There's a race condition with using the reset_pipeline var on the schema when we have both V1 and V2 pipelines running, causing a bunch of tables to not reset when I want them to (annoying)

Changes

  • Add reset_pipeline as an optional input to the workflow so I can force specific instances of the workflow to reset the pipeline instead

Does this work well for both Cloud and self-hosted?

Yes

How did you test this code?

🤷

@Gilbert09 Gilbert09 requested a review from a team January 24, 2025 20:39
@Gilbert09 Gilbert09 enabled auto-merge (squash) January 24, 2025 20:41
@Gilbert09 Gilbert09 merged commit 2265e87 into master Jan 24, 2025
93 checks passed
@Gilbert09 Gilbert09 deleted the tom/reset-pipeline-workflow branch January 24, 2025 21:05
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