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

Update-with-Start with policy Terminate-Existing #6783

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

stephanos
Copy link
Contributor

@stephanos stephanos commented Nov 8, 2024

ℹ️ Depends on #6795

What changed?

Support for Terminate-Existing workflow conflict policy in Update-with-Start.

Why?

Complete UwS' conflict policy support.

How did you test it?

Re-enabled Terminate-Existing functional tests.

Potential risks

Documentation

Is hotfix candidate?

@stephanos stephanos force-pushed the uws-terminate branch 8 times, most recently from ab543ec to 35bfb55 Compare November 11, 2024 01:22
@stephanos stephanos force-pushed the uws-terminate branch 2 times, most recently from 839e764 to e19785a Compare November 11, 2024 03:14
stephanos added a commit that referenced this pull request Nov 16, 2024
## What changed?
<!-- Describe what has changed in this PR -->

Introducing a new StartOutcome type. It signals the kind of start that
was performed.

I considered various other options (like sentinel error types and adding
a new field to the proto), but then decided on this.

## Why?
<!-- Tell your future self why have you made these changes -->

This is needed for making Terminate-Existing work, since there it's
important to distinguish between "deduped" and "reused".

See #6783

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
@stephanos stephanos marked this pull request as ready for review November 18, 2024 22:58
@stephanos stephanos requested a review from a team as a code owner November 18, 2024 22:58
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