Ansible Manage MongoDB Role

This is a simple role for just creating users in MongoDB. It can either create users for a single database or for the server as a whole.

New users are assigned database roles automatically based on the db_name. If db_name is omitted, or is "admin", the user will be given the roles root, backup, and restore. If the db_name has a value other than "admin", the user will be given the role dbOwner.

Role Variables

• db_admin — MongoDB admin username. Default: "vagrant"
• db_pass — Password for admin user. Default: "vagrant"
• new_db_user — New MongoDB user to be created
• new_db_pass — Password for new MongoDB user
• db_name — Database new user belongs to. Default: "admin"

Dependencies

This role depends on bbatsche.MongoDB-Install. You must install that role first using:

ansible-galaxy install bbatsche.MongoDB-Install

Example Playbook

- hosts: servers
  roles:
  - role: bbatsche.MongoDB-Manage
    new_db_user: mongo_user
    new_db_pass: secretPassword

License

MIT

Testing

Included with this role is a set of specs for testing each task individually or as a whole. To run these tests you will first need to have Vagrant and VirtualBox installed. The spec files are written using Serverspec so you will need Ruby and Bundler. Note: To keep things nicely encapsulated, everything is run through rake, including Vagrant itself. Because of this, your version of bundler must match Vagrant's version requirements. As of this writing (Vagrant version 1.8.1) that means your version of bundler must be between 1.5.2 and 1.10.6.

To run the full suite of specs:

$ gem install bundler -v 1.10.6
$ bundle install
$ rake

To see the available rake tasks (and specs):

$ rake -T

There are several rake tasks for interacting with the test environment, including:

• rake vagrant:up — Boot the test environment (Note: This will not run any provisioning tasks.)
• rake vagrant:provision — Provision the test environment
• rake vagrant:destroy — Destroy the test environment
• rake vagrant[cmd] — Run some arbitrary Vagrant command in the test environment. For example, to log in to the test environment run: rake vagrant[ssh]

These specs are not meant to test for idempotence. They are meant to check that the specified tasks perform their expected steps. Idempotency can be tested independently as a form of integration testing.