GitHub puppet-mongodb
91
91
47
mongodb installation

Metadata Valid
No translation
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_VERSION_RANGE}
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
With Operatingsystem Support
No translation
Supports Only Current Centos
No translation
Supports Latest Centos
No translation
Supports Only Current Debian
No translation
Supports Latest Debian
No translation
Supports Only Current Ubuntu
No translation
Supports Latest Ubuntu
No translation
In Modulesync Repo
No translation
In Plumbing
Is in plumbing
Has Secrets
Has a .sync.yml file
Synced
Has a .msync.yml file
Latest Modulesync
No translation
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
Released
Is in modulesync_config and in forge releases.
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.

Open Pull Requests

Add support for net.ssl.allowConnectionsWithoutCertificates setting in mongod.conf
enhancement
needs-tests
needs-work
tests-fail

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

Add support for net.ssl.allowConnectionsWithoutCertificates setting in mongod.conf

This Pull Request (PR) fixes the following issues

Reorder switches in dbpath_fix find command
bug
needs-feedback

Pull Request (PR) description

Fix ordering of switches in dbpath_fix's find command

This Pull Request (PR) fixes the following issues

Fixes #571

#449 separate definition of /root/.mongorc.js file
needs-work
merge-conflicts

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
separate definition of /root/.mongorc.js file
-->

This Pull Request (PR) fixes the following issues

<!--
Fixes #449
-->

catch errors based on missing authentication to allow creation of admin user on replicaset setup
merge-conflicts

Pull Request (PR) description

When setting up a new replica set with authentication enabled the puppet run fails because some exceptions were not caught properly, when getting the user and database instances. When checking if the mongodb is a primary node a recheck without authentication is done to be able to create the admin user.

This Pull Request (PR) fixes the following issues

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->

PR#182 addon: arbiter documentation + parameter replset_arbiter for mongodb::server
needs-rebase
tests-fail

The README currently does not give a hint how to configure an arbiter node for a replica set. That feature has been introduced with pull request #182.
It should also be possible to configure an arbiter by parameter replset_arbiter of mongodb::server.

Add support for replication.enableMajorityReadConcern setting
enhancement
needs-work

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

Add support for replication.enableMajorityReadConcern setting in mongod.conf.

This Pull Request (PR) fixes the following issues

542

Add default localhost real_ip
tests-fail

Pull Request (PR) description

Sometimes you just want to add a user or two to Mongo and not manage it with this module (because you're using managing it through Foreman/Katello as an example). In this case maybe all you want to do is:
```
class {'mongodb::globals':
managepackagerepo => false,
manage_package => false
}

mongodbuser { 'SOMEUSER':
ensure => present,
name => 'SOMEUSER',
password
hash => mongodbpassword('SOMEUSER', 'SOME_USER'),
database => 'admin',
roles => ['root', 'admin'],
tries => 10
}
```

Well and then you get Empty host component parsing HostAndPort from ":27017" and realize that all that's missing is just the bind_ip and that you don't want to do anything else with this module but add users... that's where this PR comes in!

This PR will add a default bind_ip of 127.0.0.1. This may be a poor hack because I don't know ruby from an implicit returning hole in the ground :) Either way, lets talk about it? maybe I'm doing something wrong? This PR seems reasonable however.

support for pure yaml in mongodb.cfg
tests-fail

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

Support for pure yaml in /etc/mongodb.cfg.
Right now only records like net.bindIp are supported, and if for example, you are using custom configuration template and your configuration looks like:
yaml
net:
port: 27017
bindIp: 0.0.0.0

you will get an error like Error: Could not prefetch mongodb_database provider 'mongodb': Could not evaluate MongoDB shell command: load('/root/.mongorc.js'); rs.slaveOk();printjson(db.getMongo().getDBs()) when using providers.
This PR adds support for both configuration file formats

This Pull Request (PR) fixes the following issues

Fixes #562 for user @seidler2547

Modulesync 4.0.0
modulesync
tests-fail