[GH-ISSUE #816] Add basic CLI commands #570

New issue

Closed

opened 2026-03-03 01:30:38 +03:00 by kerem · 10 comments

kerem commented 2026-03-03 01:30:38 +03:00

Owner

Copy link

Originally created by @xoxys on GitHub (Jan 16, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/816

It could be handy to have some basic CLI options for the bitwarden_rs binary in place. Minimum set could be something like bitwarden_rs --help and bitwarden_rs --version.

These CLI options can also be used to verify if the compiled binary is executable.

Originally created by @xoxys on GitHub (Jan 16, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/816 It could be handy to have some basic CLI options for the `bitwarden_rs` binary in place. Minimum set could be something like `bitwarden_rs --help` and `bitwarden_rs --version`. These CLI options can also be used to verify if the compiled binary is executable.

kerem 2026-03-03 01:30:38 +03:00

• closed this issue
• added the
  good first issue
  label

kerem commented 2026-03-03 01:30:39 +03:00

Author

Owner

Copy link

@tinywombat765 commented on GitHub (Mar 2, 2020):

I'd like to take this

<!-- gh-comment-id:593433230 --> @tinywombat765 commented on GitHub (Mar 2, 2020): I'd like to take this

kerem commented 2026-03-03 01:30:39 +03:00

Author

Owner

Copy link

@dani-garcia commented on GitHub (Mar 2, 2020):

Sure thing, have at it! If you need help I'm usually either here or the Matrix chat.

<!-- gh-comment-id:593539841 --> @dani-garcia commented on GitHub (Mar 2, 2020): Sure thing, have at it! If you need help I'm usually either here or the Matrix chat.

kerem commented 2026-03-03 01:30:40 +03:00

Author

Owner

Copy link

@tinywombat765 commented on GitHub (Mar 2, 2020):

@dani-garcia Do you have a preference as for as cli argument parsing is concerned?

<!-- gh-comment-id:593575346 --> @tinywombat765 commented on GitHub (Mar 2, 2020): @dani-garcia Do you have a preference as for as cli argument parsing is concerned?

kerem commented 2026-03-03 01:30:40 +03:00

Author

Owner

Copy link

@dani-garcia commented on GitHub (Mar 2, 2020):

Do you mean choice of library? If nothing has changed, clap is the most popular so I'd go that way.

https://github.com/clap-rs/clap

<!-- gh-comment-id:593577236 --> @dani-garcia commented on GitHub (Mar 2, 2020): Do you mean choice of library? If nothing has changed, clap is the most popular so I'd go that way. https://github.com/clap-rs/clap

kerem commented 2026-03-03 01:30:40 +03:00

Author

Owner

Copy link

@tinywombat765 commented on GitHub (Mar 2, 2020):

In that case I'd like to use structopt, which is built on top of clap but provides a nicer api imo

<!-- gh-comment-id:593577827 --> @tinywombat765 commented on GitHub (Mar 2, 2020): In that case I'd like to use structopt, which is built on top of clap but provides a nicer api imo

kerem commented 2026-03-03 01:30:40 +03:00

Author

Owner

Copy link

@dani-garcia commented on GitHub (Mar 2, 2020):

Ah, I thought the structopt api was merged into clap too, but apparently that's scheduled to be released on the next version of clap 3.0!

I agree the declarative api of structopt is nicer, I'd prefer to use that too.

<!-- gh-comment-id:593579909 --> @dani-garcia commented on GitHub (Mar 2, 2020): Ah, I thought the structopt api was merged into clap too, but apparently that's scheduled to be released on the next version of clap 3.0! I agree the declarative api of structopt is nicer, I'd prefer to use that too.

kerem commented 2026-03-03 01:30:40 +03:00

Author

Owner

Copy link

@tinywombat765 commented on GitHub (Mar 2, 2020):

I see that if the GIT_VERSION environment var is set at compile time the app with print that as it's version. Should I use that for the version flag? If so what should it print if anything it that var is not set? And if not what should I print?

<!-- gh-comment-id:593584708 --> @tinywombat765 commented on GitHub (Mar 2, 2020): I see that if the GIT_VERSION environment var is set at compile time the app with print that as it's version. Should I use that for the version flag? If so what should it print if anything it that var is not set? And if not what should I print?

kerem commented 2026-03-03 01:30:40 +03:00

Author

Owner

Copy link

@dani-garcia commented on GitHub (Mar 2, 2020):

For the version flag I'd just print bitwarden_rs followed by a space and the GIT_VERSION value if present. Similar to how cargo --version or rustc --version do it.

If no version is provided, you could print something like.

bitwarden_rs (Version info from Git not present)

<!-- gh-comment-id:593589845 --> @dani-garcia commented on GitHub (Mar 2, 2020): For the version flag I'd just print `bitwarden_rs` followed by a space and the GIT_VERSION value if present. Similar to how cargo --version or rustc --version do it. If no version is provided, you could print something like. ``` bitwarden_rs (Version info from Git not present) ```

kerem commented 2026-03-03 01:30:40 +03:00

Author

Owner

Copy link

@tinywombat765 commented on GitHub (Mar 2, 2020):

I opened a PR #888

<!-- gh-comment-id:593594279 --> @tinywombat765 commented on GitHub (Mar 2, 2020): I opened a PR #888

kerem commented 2026-03-03 01:30:40 +03:00

Author

Owner

Copy link

@dani-garcia commented on GitHub (Mar 2, 2020):

Closed because #888 got merged

<!-- gh-comment-id:593671687 --> @dani-garcia commented on GitHub (Mar 2, 2020): Closed because #888 got merged

kerem referenced this issue 2026-03-03 08:52:55 +03:00

[PR #571] [MERGED] Added reqwest proxy support #2755

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

revert-7033-patch-1

cached-config-operations

test_dylint

1.35.7

1.35.6

1.35.5

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels   

SSO

  

Third party

  

better for forum

  

bug

  

bug

  

documentation

  

duplicate

  

enhancement

  

future Vault

  

future Vault

  

future Vault

  

good first issue

  

help wanted

  

low priority

  

notes

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

troubleshooting

  

wontfix

No labels

SSO

Third party

better for forum

bug

bug

documentation

duplicate

enhancement

future Vault

future Vault

future Vault

good first issue

help wanted

low priority

notes

pull-request

question

troubleshooting

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/vaultwarden#570

No description provided.