Use proper yaml for the mongod config

[stevenpost]

It turns out that not properly doing this caused authenthication not being properly disabled on later versions.

[h-haaks]

You have to handle the 'config_data' ( additional config ) some how in the template.
If someone starts to add propper yaml hashes to it it will generate duplicate key in the config file.

Might be possible to generate a complete ruby hash from all the params and then use to_yaml() on that.

[stevenpost]

You have to handle the 'config_data' ( additional config ) some how in the template. If someone starts to add propper yaml hashes to it it will generate duplicate key in the config file.

Might be possible to generate a complete ruby hash from all the params and then use to_yaml() on that.

Using to_yaml was my first thought, but it proved a bit difficult to properly implement in the mongodb::config class. If you do decide to go down the path of using a hash for config (not totally against it) it would make things easier for us... but also make it way more easy to shoot yourself in the foot. Then again, I think sysadmins using Puppet are expected to know what they are doing...

It would be a major break though.

[stevenpost]

Superseeded by #735