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

StartWorkflow with VersioningOverride #6891

Merged
merged 11 commits into from
Nov 27, 2024
Merged

Conversation

carlydf
Copy link
Contributor

@carlydf carlydf commented Nov 26, 2024

What changed?

Set Versioning Override in new mutable state created on StartWorkflowExecution and SignalWithStartWorkflowExecution

Why?

So that users can run workflows on specific deployments without needing to run all new unpinned workflows on that deployment. Enables canary workflows for versioning.

How did you test it?

Functional tests that set and get the versioning override.

Potential risks

Documentation

Is hotfix candidate?

@carlydf carlydf requested a review from a team as a code owner November 26, 2024 06:20
@carlydf carlydf changed the title StartWorkflowExecution with VersioningOverride StartWorkflow with VersioningOverride Nov 26, 2024
service/history/workflow/mutable_state_impl.go Outdated Show resolved Hide resolved
service/worker/deployment/deployment_client.go Outdated Show resolved Hide resolved
Copy link
Member

Choose a reason for hiding this comment

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

I need to go through these tests after merge.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hopefully they will be cleaner by then

@carlydf carlydf merged commit 65f9600 into versioning-3 Nov 27, 2024
33 of 47 checks passed
@carlydf carlydf deleted the cdf/startwithoverride branch November 27, 2024 01:43
ShahabT pushed a commit that referenced this pull request Nov 27, 2024
## What changed?
Set Versioning Override in new mutable state created on
StartWorkflowExecution and SignalWithStartWorkflowExecution

## Why?
So that users can run workflows on specific deployments without needing
to run all new unpinned workflows on that deployment. Enables canary
workflows for versioning.

## How did you test it?
Functional tests that set and get the versioning override.

## 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) -->
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.

3 participants