search

CHIMEFRB / workflow

🌊 Working in flowstate.
0 stars 0 forks source link

94 feat improve cli commands #100

Closed odarotto closed 3 months ago

chrisfandrade16 commented 3 months ago

Just curious, did you decide on any way to show the deployments with the worflow CLI, or shall we make a separate issue for that?

chrisfandrade16 commented 3 months ago

Another question: is it possible to get a single pipeline simply by its name only? Or, can there be mulitple pipelines with the same name? It might be easier for users to remember the name, than the ids. And so, if the names are unique, allowing either the name or id to be used in the CLI (but not needing both, as this PR addressed), could be useful.

odarotto commented 3 months ago

Just curious, did you decide on any way to show the deployments with the worflow CLI, or shall we make a separate issue for that?

Yes I will create separate issue for this.

odarotto commented 3 months ago

Another question: is it possible to get a single pipeline simply by its name only? Or, can there be mulitple pipelines with the same name? It might be easier for users to remember the name, than the ids. And so, if the names are unique, allowing either the name or id to be used in the CLI (but not needing both, as this PR addressed), could be useful.

Since a Config can generate several pipelines, all of these pipelines live under the same name, also a user can send 2 Config with the same name but that generate different pipeline. I think for Config we should leave the requirement for and for Pipeline use only the .