Pin rabbitmq versions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
As per suggestion to https://github.com/StackStorm/ansible-st2/pull/291, we should pin rabbitmq version (and erlang on EL8), so that the version is known.
This should be performed on all installers.
It is particular relevant to EL8 which takes the version from packagecloud.
Once we pin versions, we can then update documentation to list recommended RabbitMQ versions as per suggestion on https://github.com/StackStorm/st2docs/pull/1063
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 installer changes discussed in ansible-st2/pull/291 and identify every installer that provisions RabbitMQ, with special attention to Erlang on EL8 and packagecloud. Pin the RabbitMQ and required Erlang versions consistently across installers, then verify that the versions are known and ready to be reflected in the documentation mentioned in st2docs/pull/1063.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, erlang, rabbitmq
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100