-
Notifications
You must be signed in to change notification settings - Fork 141
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
feat(console): blob share ticket #1746
feat(console): blob share ticket #1746
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some small language nits in documentation, but this feature is great. thanks again for a super thorough PR!
@b5 changing this to draft because setting recursive by default won't work. It seems to be that to know if the blob is a collection or not we need to look into tags for tagged data. Not sure how for untagged data |
Description
Adds a subcommand to blob to produce a ticket. Option include:
Notes & open questions
I believe the generated tickets are correct (if they are not, then there is no validation about it) but some of them don't seem to work, for example if the ticket is direct address only. We should debug this afterwards
Sample output:
Change checklist