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.

Sign up for GitHub

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

Jump to bottom

Implement store get in the CLI #198

Open
Tracked by #205
alilleybrinker opened this issue Aug 23, 2024 · 0 comments
Open
Tracked by #205

Implement store get in the CLI #198

alilleybrinker opened this issue Aug 23, 2024 · 0 comments
Labels
crate: omnibor-cli Relating to the omnibor-cli crate good first issue Good for newcomers type: feature New feature or request

Comments

@alilleybrinker
Copy link
Member

Similar to #197, but for just a single manifest, it would be great if we could get the contents of a manifest out. By default, for consistency with the expectations of most CLIs, it should write the manifest to stdout. The command should also take an -o/--output flag to direct the output to a file, and of course the user could redirect stdout instead.
@alilleybrinker alilleybrinker added type: feature New feature or request good first issue Good for newcomers crate: omnibor-cli Relating to the omnibor-cli crate labels Aug 23, 2024
@alilleybrinker alilleybrinker mentioned this issue Aug 23, 2024
Open
5 tasks
@alilleybrinker alilleybrinker moved this to Backlog in OmniBOR Rust Sep 9, 2024
@alilleybrinker alilleybrinker changed the title Implement manifest get in the CLI Implement store get in the CLI Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
crate: omnibor-cli Relating to the omnibor-cli crate good first issue Good for newcomers type: feature New feature or request
Projects
OmniBOR Rust
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alilleybrinker