-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
Workflow quick authoring
-
False
-
-
False
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
-
Assumptions:
- A workflow (as a ) has already been defined, and is stored in a Git repository
- This Git repository has already a CI/CD pipeline defined where each code modification produces a new container image and deploys it.
- The orchestrator-backend can interact programatically with the workflow's Git repository.
We could offer a similar experience, a la GitHub Actions, where after editing a workflow definition the user is prompted to commit the changes.
Here is an example of the prompt displayed after editing a GitHub Action definition file:
- depends on
-
KOGITO-9913 Support multiple profiles for devmode and prod for admin
- Open
- is incorporated by
-
FLPATH-764 Orchestrator plug-in UI/UX
- Closed
- is related to
-
FLPATH-990 Component Workflows Tab
- Refinement
-
FLPATH-991 Auto Register Orchestrator Workflows as entities
- Closed
There are no Sub-Tasks for this issue.