<!--
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
<!--
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
-->
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.
Pull Request (PR) description
Fix ordering of switches in dbpath_fix's find command
This Pull Request (PR) fixes the following issues
Fixes #571
<!--
Thank you for contributing to this project!
-->
Pull Request (PR) description
Added the mechanism parameter for the passwordhash command
```
def passwordhash=(value)
if dbismaster
command = {
updateUser: @resource[:username],
pwd: @resource[:passwordhash],
digestPassword: false
}
command[:mechanisms] = @resource[:authmechanism] == :scramsha1 ? ['SCRAM-SHA-1'] : ['SCRAM-SHA-256']
mongoeval("db.runCommand(#{command.tojson})", @resource[:database])
else
Puppet.warning 'User password operations are available only from master host'
end
end
```
Changed unit test for mongodbuser due to new expected line generated for passwordhash command.
This Pull Request (PR) fixes the following issues
Fixes #649
An initial puppet run (eg. in a vagrant box) will produce an error while trying to resolve the mongodbversion fact:
```
Facter: error while resolving custom fact "mongodbversion": undefined method '[]' for nil:NilClass
```
The reason is that the check for the existence of the mongo binary is inside the setcode block.
This pull request uses the fact confinement mechanism to pre-empt the fact resolution if the mongo binary is not available.
Pull Request (PR) description
Fix for several issues: SSL, Replicaset initialization, Secondary checking, etc..
This Pull Request (PR) fixes the following issues
Enable MongoDB 5.0 support
Fix mongorcjs typo
Fixed mongorc.js type for secondary check
Add support for Mongo 4.x secondary check
Fix SSL support for MongoDB 4.x
Fix for MongoDB v4 Replica Set initialization
Pull Request (PR) description
Using Amazon specific package repos when os name is amazon.
<!--
Thank you for contributing to this project!
-->
Pull Request (PR) description
Added slack Integration to fix a know bug in OpsManager 4.4 in conf-mms.properties file
<!--
-->
This Pull Request (PR) fixes the following issues
Ops Manager 4.4. has known issue with slack integration. We contact support and they asked us to do couple
configurations which apparently are not in this monog module. Theses two settings are slack client id and client secret #### for slack integration.
<!--
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
…while auth is enabled
<!--
Thank you for contributing to this project!
-->
Pull Request (PR) description
On arbitrator servers you get the following message when auth is enabled:
Notice: /Stage[main]/Mongodb::Replset/Mongodb_replset[example_set]/ensure: created (corrective)
Warning: Host mongoarb01:27017 is available, but you are unauthorized because of authentication is enabled: true
In debug mode you can see:
```
Debug: Request failed: 'Execution of '/usr/bin/mongo admin --quiet --host 127.0.0.1:27017 --eval load('/root/.mongorc.js'); printjson(rs.conf())' returned 252: uncaught exception: Error: Could not retrieve replica set config: {
"ok" : 0,
"errmsg" : "not authorized on admin to execute command { replSetGetConfig: 1.0, lsid: { id: UUID(\"a2213cd2-e6c4-4d15-bf29-d01b7a54a838\") }, $db: \"admin\" }",
"code" : 13,
"codeName" : "Unauthorized"
} :
```
The admin user has all the needed rights but this errmsg keeps telling us it has not.
For this reason I created a variable so we can disable this class on our arbitrator nodes by setting:
mongodb::replset::sets_creation: false
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
-->
Currently the mongodb command updateUser defaults to SCRAM-SHA-256 but you can't update these passwords.
And also show an error when the update goes wrong.
<!--
Thank you for contributing to this project!
-->
Pull Request (PR) description
Currently the mongodb command updateUser defaults to SCRAM-SHA-256 but you can't update these passwords.
So now set the correct mecahnisms and handle the response of the command. So if you try to update this hash with SCRAM-SHA-256 you will see an error message. If you use scram_sha_1 it will update the password and continue like it should.
This Pull Request (PR) fixes the following issues
Fixes #649
Fixes https://github.com/voxpupuli/puppet-mongodb/pull/650
<!--
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
Pull Request (PR) description
As this module now support the latest mongodb versions the default repo version should reflect this.
This Pull Request (PR) fixes the following issues
Fixes #754
