Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is this still maintained and used? Alternatives? #241

Open
sezanzeb opened this issue Oct 12, 2020 · 7 comments
Open

Is this still maintained and used? Alternatives? #241

sezanzeb opened this issue Oct 12, 2020 · 7 comments

Comments

@sezanzeb
Copy link

The PR for 4.2 was merged within two days: #176

The PR for 4.4 has been open for almost a month: #235

Is this repo obsolete or not really used anymore or something? What are people using nowadays to get up to date mongodbs in their ansible config?

@smutel
Copy link

smutel commented Nov 3, 2020

I am using this repo but I have the same thought than you.
I created a PR, no answer ...
Now I need this feature which is not merged ...

@Perni1984
Copy link

cc @UnderGreen would you be interested in additional maintainers of this package? I would volunteer.

@UnderGreen
Copy link
Owner

Slowly.. Once in 3-4 months, I take a look at issues/PRs. Too busy on the main job.
@Perni1984 I don't see anything in your profile about Ansible. I don't want to left this role to the first person asking it to be honest.

@Perni1984
Copy link

Perni1984 commented Nov 7, 2020

@UnderGreen no problem, I just wanted to offer my help supporting you either myself or creating a team of maintainers. As a matter of fact I am working with Ansible for ~ 12 month, but have several years experience with Puppet, Chef and setting up scalable multi-server clustered environments before the well known devops tools got popular. Other than that, I am sure that there are people out there that have deeper knowledge of Ansible than me.

Workaround for people needing some PRs merged sooner:
Just create a fork of the repo and add the relevant PRs to your own fork (https://stackoverflow.com/questions/6022302/how-to-apply-unmerged-upstream-pull-requests-from-other-forks-into-my-fork).

In your requirements.yml file you can then specify your own forked repo and the relevant branch like this:

---

roles:
  - name: undergreen.mongodb
    src: https://github.com/pcode-at/ansible-role-mongodb <--- path to your forked repo
    version: master

@UnderGreen
Copy link
Owner

I will take a look asap your PR. It didn't go through testing for some reason.

@UnderGreen
Copy link
Owner

Fixed lately a lot of issues and add multiple enhancements.

I believe mongodb collection is supposed to replace this role in future, but I will continue support this one if there is still any interest from users.

@csuka
Copy link

csuka commented Jan 17, 2022

Alternative: https://github.com/csuka/ansible_role_mongodb
^ Using official modules, and a future proof configuration. Compatible with most versions, only for EL 8-like systems tho.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants