-
Notifications
You must be signed in to change notification settings - Fork 614
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
postgresql::postgres_password throws errors when Deferred #1575
Comments
Is this a duplicate of #1560? |
I'm going to go with, no. I'm Deferring function 'postgresql::postgresql_password':
Issue #1560 is passing in a Deferred to the class.
|
are you sure that's not the case? |
Yes. Deferred can't resolve this:
So even though I'm providing values - and avoiding the Puppet function -- it still fails. Note: I'm appearing as my work identity rather than my personal login. |
Can you provide a PR that switches to native Enum? |
I'll try and figure out how to do that. (First time.) Going to have to do it off work hours due to the bureaucracy that is my current employer and our client. |
Describe the Bug
When
postgresql::postgres_password
is Deferred, it throws one of two possible errors:Error 1:
Error 2:
Expected Behavior
A clear and concise description of what you expected to happen.
Expectation 1:
When function
postgresql::postgresql_password
is Deferred and only passedusername
andpassword
, the function should use the built in defaults without throwing an error.Expectation 2:
When function
postgresql::postgresql_password
is Deferred and values are provided forusername
,password
,sensitive
, andhash
, the function should not throw a type error.Steps to Reproduce
Steps to reproduce the behavior:
Environment
Additional Context
Add any other context about the problem here.
Under postgresql 9.2.0, we did not provide
sensitive
andhash
values and the function worked when Deferred.The text was updated successfully, but these errors were encountered: