You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using fly, I have to specify the target and my pipeline / build / ... and remember the options.
What would make this better?
fly hijack can take an url and not need anything else to know which target / pipeline / build to use. This option is only available for hijack command.
-u, --url= URL for the build, job, or check container to hijack
Generalising this option to other commands to get the target and other info needed would be helpful.
In my case, the two commands where it would help me the most is get-pipeline and set-pipeline
commands where fly could retrieve the target and pipeline from the URL:
checklist
destroy-pipeline
expose-pipeline
get-pipeline
hide-pipeline
jobs
pause-pipeline
rename-pipeline
resources
set-pipeline
unpause-pipeline
commands where fly could retrieve the target and job from the URL:
pause-job
trigger-job
unpause-job
commands where fly could retrieve the target and extra info from the URL:
abort-build (build or pipeline / job)
check-resource (pipeline and resource)
check-resource-type (pipeline and resource type)
clear-task-cache (pipeline and job, would still need step)
resource-versions (pipeline and resource)
watch (build or pipeline / job)
Are you interested in implementing this yourself?
Yes ! I can start with the commands on pipelines
The text was updated successfully, but these errors were encountered:
What challenge are you facing?
When using
fly
, I have to specify the target and my pipeline / build / ... and remember the options.What would make this better?
fly hijack
can take anurl
and not need anything else to know which target / pipeline / build to use. This option is only available forhijack
command.Generalising this option to other commands to get the target and other info needed would be helpful.
In my case, the two commands where it would help me the most is
get-pipeline
andset-pipeline
commands where
fly
could retrieve the target and pipeline from the URL:checklist
destroy-pipeline
expose-pipeline
get-pipeline
hide-pipeline
jobs
pause-pipeline
rename-pipeline
resources
set-pipeline
unpause-pipeline
commands where
fly
could retrieve the target and job from the URL:pause-job
trigger-job
unpause-job
commands where
fly
could retrieve the target and extra info from the URL:abort-build
(build or pipeline / job)check-resource
(pipeline and resource)check-resource-type
(pipeline and resource type)clear-task-cache
(pipeline and job, would still need step)resource-versions
(pipeline and resource)watch
(build or pipeline / job)Are you interested in implementing this yourself?
Yes ! I can start with the commands on pipelines
The text was updated successfully, but these errors were encountered: