-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
pulsar-shell persistent modes #21194
Open
1 of 2 tasks
flowchartsman opened this issue
Sep 16, 2023
· 1 comment
· May be fixed by cognitree/pulsar#6 or #22522
Open
1 of 2 tasks
pulsar-shell persistent modes #21194
flowchartsman opened this issue
Sep 16, 2023
· 1 comment
· May be fixed by cognitree/pulsar#6 or #22522
Labels
help wanted
Stale
type/enhancement
The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages
Comments
flowchartsman
added
the
type/enhancement
The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages
label
Sep 16, 2023
The issue had no activity for 30 days, mark with Stale label. |
This was referenced Apr 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
help wanted
Stale
type/enhancement
The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages
Search before asking
Motivation
Using pulsar-shell interactively, it's kind of a pain to prefix everything with
admin
. I think it would be nice if the command acceptedadmin
andclient
on their own as special commands that put the command into that mode with an implicit prefix.Solution
Allow
admin
andclient
, when passed on their own to enter into admin or client mode respectively, with the addition of one more commandexitmode
to return to the base state. These modes would not persist between sessions.Alternatives
No response
Anything else?
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: