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

As a workflow manager I want to be able to identify the version of a deployed workflow #125

Open
jeremythuff opened this issue Jan 23, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@jeremythuff
Copy link
Member

jeremythuff commented Jan 23, 2024

Currently there is no way to identify what version of a workflow is running in the workflow engine. When a workflow is activated it should always include a variable with the workflow version.

The property that must be populated is here: https://github.com/TAMULib/mod-workflow/blob/main/components/src/main/java/org/folio/rest/workflow/model/Workflow.java#L40

This work has two main components:

  1. Mod Workflow needs to be modified to ensure that the version property is added to all deployed workflows as a process variable.
  2. This will also require edits to the FW CLI to pass up the fw-registry commit hash as the version tag for all built workflows.

Version Tag property on w/f
(commit hash of the deployed w/f)

@jeremythuff jeremythuff converted this from a draft issue Jan 23, 2024
@jeremythuff jeremythuff added the enhancement New feature or request label Jan 23, 2024
@jeremythuff jeremythuff moved this from 📋 Backlog to 👷 In Planning in FOLIO Jan 23, 2024
@rmathew1011 rmathew1011 moved this from 👷 In Planning to 🏃 On Sprint in FOLIO Jan 25, 2024
@jeremythuff jeremythuff moved this from 🏃 On Sprint to 📋 Backlog in FOLIO Apr 16, 2024
rmathew1011 added a commit that referenced this issue Nov 12, 2024
Unit tests created for prePersist()
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant