RabbiMQ validation: Hard dependency on package manager for version check
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 119
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Description
During deployment the RabbitMQ version gets validated. This is done by `dpkg -s rabbitmq-server | grep Version`. This adds a hard dependency on a) Debian package manager (excluding RHEL/CentOS and container setups) and b) an installation of RabbitMQ on the web server, which in high scale setups usually runs on a separate server/container.
While the version check outputs only a warning, the version check can be implemented in a better way in PHP (see #804).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing deployment version-validation flow and issue #804, then locate where `dpkg -s rabbitmq-server | grep Version` is invoked. The change is complete when version validation no longer requires Debian's package manager or a local RabbitMQ installation and still reports the intended warning across supported deployment setups.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100