-
Notifications
You must be signed in to change notification settings - Fork 230
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
Make database_password an optional parameter #78
Conversation
|
Merged build triggered. (Status: PENDING, Details: null) |
|
Merged build started. (Status: PENDING, Details: http://box.bob.sh:8080/job/puppetlabs-puppetdb/181/) |
|
Merged build finished. (Status: SUCCESS, Details: http://box.bob.sh:8080/job/puppetlabs-puppetdb/181/) |
In some cases it may not be possible to securely specify a password for PuppetDB. When that is true, it's impossible to use the module to manage PuppetDB, because specifying undef for the password will cause database validation to fail, or for the setting in database.ini to be overridden. This change will simply check that database_password is set, and will skip validation and changing database.ini in the case where it is not.
|
Closing this since it shouldn't be against master. |
|
Actually, that works. |
|
Build triggered. (Status: PENDING, Details: null) |
|
Merged build started. (Status: PENDING, Details: http://box.bob.sh:8080/job/puppetlabs-puppetdb/182/) |
|
Merged build finished. (Status: SUCCESS, Details: http://box.bob.sh:8080/job/puppetlabs-puppetdb/182/) |
|
Updated so it should merge clean. |
Make database_password an optional parameter
In some cases it may not be possible to securely specify a password for
PuppetDB. When that is true, it's impossible to use the module to manage
PuppetDB, because specifying undef for the password will cause database
validation to fail, or for the setting in database.ini to be overridden.
This change will simply check that database_password is set, and will skip
validation and changing database.ini in the case where it is not.