[fix][cli] Pulsar shell: support relative paths (cliextensions) #17648
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
The
pulsar-shell
script doesn't change the working directory to the Pulsar home one. In this way if you configurecliExtensionsDirectory
with a relative path, it only works if you run pulsar-shell from the pulsar home directory. For instancecd bin && ./pulsar-shell
is not able to find the cli extensions dir.Modifications
The only disadvantage is that the
--file
autocompletion will suggest files from the Pulsar home directory and not fromthe real working dir. (but it's still better than the current behaviour)
doc-not-needed