From 40a6a6f9117da6114d3e603295929b339cf153ba Mon Sep 17 00:00:00 2001 From: Scott Sturdivant Date: Wed, 14 May 2014 07:49:11 -0600 Subject: [PATCH] Clarify that the encrypted param must also be set. While the encrypted parameter's documentation clearly states that it needs to be set, if you are focused on the password parameter's documentation, there's nothing to draw your attention to the fact that encrypted may also need to be set. --- database/postgresql_user | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/database/postgresql_user b/database/postgresql_user index 1dda1a6dc57..8af8c45d0c5 100644 --- a/database/postgresql_user +++ b/database/postgresql_user @@ -44,7 +44,7 @@ options: password: description: - set the user's password, before 1.4 this was required. - - "When passing an encrypted password it must be generated with the format C('str[\\"md5\\"] + md5[ password + username ]'), resulting in a total of 35 characters. An easy way to do this is: C(echo \\"md5`echo -n \\"verysecretpasswordJOE\\" | md5`\\")." + - "When passing an encrypted password, the encrypted parameter must also be true, and it must be generated with the format C('str[\\"md5\\"] + md5[ password + username ]'), resulting in a total of 35 characters. An easy way to do this is: C(echo \\"md5`echo -n \\"verysecretpasswordJOE\\" | md5`\\")." required: false default: null db: