This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
Conductor CLI #2560
NickTomlin
started this conversation in
Ideas
Conductor CLI
#2560
Replies: 1 comment 1 reply
-
when i do changes in this .json files in conductor-resources /workflow.recorder.initiated.regestration.json and triggered the pipeline and when i see in conductor ui ,i dont see the changes affected in the UI but when i do any changes in .ts file ,conductor ui is picking up changes done in .json files. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been using a node.js based
cli
to simplify my conductor workflow and wanted to share it with you all to get some feedback. Here's a quick video overview:Conductor CLI demo - Watch Video
Feature overview
(if you don't want to wait for the video, here's a brief text overview)
Running workflows
This is the feature I personally use the most, it's helpful to have a quick feedback loop when running workflow definitions.
Opening in the
conductor
UIThe
workflow:run
command takes an--open
flag that opens the workflow execution in the conductor UI.Updating workflow and task metadata
Use cases
❓ Questions ❓
I'm interested in opinions here, is this worth open sourcing? Are there different directions we should head in?
Beta Was this translation helpful? Give feedback.
All reactions