candlerb opened a new issue #5650: pulsar-admin: avoid changing working directory URL: https://github.com/apache/pulsar/issues/5650 **Is your feature request related to a problem? Please describe.** When pulsar-admin starts, the first thing it does is [change the working directory](https://github.com/apache/pulsar/blob/master/bin/pulsar-admin#L26). This causes several problems. (1) Any filename you give on the command line cannot be in the current directory ``` $ ls womble.yaml womble.yaml $ pulsar-admin functions create --function-config-file womble.yaml womble.yaml (No such file or directory) ``` 2. Even if you give an absolute path on the command line, any path *within* the function-config-file also cannot be in the current directory ``` $ ls func1.py womble.yaml func1.py womble.yaml $ cat womble.yaml tenant: public namespace: default name: womble py: func1.py className: func1.FirstFunction inputs: [my-topic] $ apache-pulsar-2.4.1/bin/pulsar-admin functions create --function-config-file /home/ubuntu/womble.yaml The specified python file does not exist ``` **Describe the solution you'd like** Not to change directory. There must be some reason for it - there is a comment saying `Change to PULSAR_HOME to support relative paths` - but I'm not sure what it means by that. Is it working around some Java implementation issue? If changing directory makes it more convenient for pulsar itself, it makes it less convenient for the user of pulsar. **Describe alternatives you've considered** Using pulsarctl instead - but that's not fully baked yet. **Additional context** N/A
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
