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

feat(ui): add ability to replay executions with latest flow revision #5917

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from

Conversation

RudhraBharathy
Copy link
Contributor

Add Option for "Replay Using Latest Revision" in Bulk Actions

Closes: #5740

Summary of Changes

This update introduces a new button, "Replay Using Latest Revision," in the bulk actions section of Kestra. It allows users to replay multiple executions using the most recent version of each flow, instead of using the original revision initially used when the execution was triggered.

Key Differences from Regular Replay

  • Regular Replay:

    • Replay executions using the original flow revisions.
  • Latest Revision Replay:

    • Uses the most recent version of each flow.
    • Requires fetching the latest revision information for each flow before execution.
    • Ensures that multiple executions of the same flow use the same, latest revision.

This feature allows users to replay executions with up-to-date versions of the flows, regardless of the original revision used during the initial execution.

QA Process

The following quality assurance steps have been completed to verify the feature:

  1. Verified the placement and functionality of the "Replay Using Latest Revision" button in the bulk actions interface.
  2. Tested that executions are replayed using the latest flow versions when the option is selected.
  3. Confirmed that regular replay behavior uses the original flow revisions by default.

Setup Instructions

  1. Navigate to the Executions section select the bulk actions section and confirm the presence and functionality of the "Replay Using Latest Revision" button.
  2. Test the new functionality to ensure executions are replayed using the most recent flow versions.

@MilosPaunovic MilosPaunovic self-assigned this Nov 14, 2024
@MilosPaunovic MilosPaunovic self-requested a review November 15, 2024 07:09
@anna-geller
Copy link
Member

@MilosPaunovic can we merge it?

@MilosPaunovic
Copy link
Member

We'll be able to, once I get the chance to review it properly.

@MilosPaunovic
Copy link
Member

It seems like we miss the backend part of this issue, as of right now we changed only the UI, but the data is sent in the same manner.

Will assign this issue to @Skraye, so he can add the Java part to it and after do the review of the FE, also. He'll be off for some time, but it will be reviewed @RudhraBharathy, don't worry.

@MilosPaunovic MilosPaunovic requested review from Skraye and removed request for MilosPaunovic December 6, 2024 11:14
@MilosPaunovic MilosPaunovic assigned Skraye and unassigned MilosPaunovic Dec 6, 2024
@MilosPaunovic
Copy link
Member

Hi @RudhraBharathy, could you please try to resolve the merge conflict which turned up in the meantime?

@RudhraBharathy
Copy link
Contributor Author

Sure @MilosPaunovic, let me look into the merge conflict and try to resolve it.

@MilosPaunovic MilosPaunovic removed the request for review from Skraye January 16, 2025 12:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: To review
Development

Successfully merging this pull request may close these issues.

Add the option to use the latest revision when starting Replay in bulk actions
4 participants