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

Generalising url option to fly commands #3660

Open
20 tasks
mockersf opened this issue Apr 1, 2019 · 1 comment
Open
20 tasks

Generalising url option to fly commands #3660

mockersf opened this issue Apr 1, 2019 · 1 comment

Comments

@mockersf
Copy link
Contributor

mockersf commented Apr 1, 2019

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 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

@vito
Copy link
Member

vito commented Apr 3, 2019

Sounds nice. It'd be great if there was some way to do this generically so all the commands don't require too much code to handle it. 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants