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

Re-do the CLI again #405

Open
gijzelaerr opened this issue Jul 28, 2021 · 3 comments
Open

Re-do the CLI again #405

gijzelaerr opened this issue Jul 28, 2021 · 3 comments
Assignees
Labels
planned-go Planned to be fixed with the Go library
Milestone

Comments

@gijzelaerr
Copy link
Collaborator

the current CLI works, but can be more user-friendly

@gijzelaerr gijzelaerr added this to the 2.3 milestone Aug 25, 2021
@gijzelaerr gijzelaerr modified the milestones: 2.3, 2.4 Apr 22, 2022
@jwijenbergh jwijenbergh added the planned-go Planned to be fixed with the Go library label Jun 13, 2022
@jwijenbergh jwijenbergh changed the title Improve CLI Document CLI Mar 6, 2023
@jwijenbergh
Copy link
Collaborator

The CLI has been rewritten, interactive mode "eduvpn-cli interactive" should be pretty user friendly but the normal CLI needs documentation

@jwijenbergh jwijenbergh modified the milestones: 4.0, 4.1 Mar 6, 2023
@jwijenbergh jwijenbergh modified the milestones: 4.1, 4.2 Apr 19, 2023
@mmahmoudian
Copy link

The interactive subcommand is heavily missing the point of the major use-case of a CLI. The CLI is usually used for automation and scripting. Therefore, the interactive is useless in 100% of automation use-cases, and it is only and only helpful if one wants to use it as an alternative to GUI.

Having manpage, infopage, better error and messaging and clarifying the steps for the sake of logging and finding the point of failure is what that can improve the CLI experience imho.

Maybe at some point I add manpage and add the missing documentation.

@jwijenbergh
Copy link
Collaborator

The interactive subcommand is heavily missing the point of the major use-case of a CLI. The CLI is usually used for automation and scripting. Therefore, the interactive is useless in 100% of automation use-cases, and it is only and only helpful if one wants to use it as an alternative to GUI.

That's exactly why it's been made, as an alternative to the GUI. For scripting there are a bunch of flags that you can use. The reason why I have not extensively documented these outside of --help is that I am not super happy with them. I think I have to rewrite the CLI again but this time make a document of how it should work beforehand

@jwijenbergh jwijenbergh changed the title Document CLI Re-do the CLI again Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
planned-go Planned to be fixed with the Go library
Projects
None yet
Development

No branches or pull requests

3 participants