Can extended environment variables be taken into account by CLI tools?
michaelklishin opened this issue · 0 comments
michaelklishin commented
This is a semi-speculative idea inpired by this rabbitmq-users thread.
TL;DR: the deep startup refactoring backported from master into 3.8.4 may have changed what environment variables CLI tools use when computing default target node name.
Can or should we try to reuse rabbit_env in CLI tools? If not, at the very least this function should take NODENAME into account as well as RABBITMQ_NODENAME (which did work for the OP in the thread above).