-
-
Notifications
You must be signed in to change notification settings - Fork 267
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
Fpm config results in "expects a Hash value, got Tuple" #536
Comments
I can confirm this. Line 103 in
The merge strategy
The lookup should return a hash since the value is used as parameter for I would suggest to use the |
Same issue. Puppet: 6, CentOS 7 |
When allowing configuring `php::fpm::pools` as hashes in Hiera, the `unique` ("array merge") behavior will fail for hashes. Just use the `deep` merge behavior to return a merged hash. Closes voxpupuli#536.
Puppet documentation states `unique` ("array merge") behavior will return a merged array and will fail for hashes. We can instead rework this lookup function to automatically lookup the variables as per current best practises. This change is in line with b188888. Closes voxpupuli#536.
We are also seeing this bug. Any chance for a quick fix/release? :) |
Puppet documentation states `unique` ("array merge") behavior will return a merged array and will fail for hashes. We can instead rework this lookup function to automatically lookup the variables as per current best practises. This change is in line with b188888. Closes voxpupuli#536.
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
In the manifest:
include ::php
In the hiera config:
What are you seeing
Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Found value has wrong type, expects a Hash value, got Tuple (file: /etc/puppetlabs/code/environments/php
update/modules/php/manifests/fpm.pp, line: 103, column: 17)
What behaviour did you expect instead
The pool config should have been pushed to the node. Whatever I change to the hiera config, it always ends with the same error.
Output log
See above
Any additional information you'd like to impart
This behaviour is seen since the new module version is released. With the old version there are no issues.
The text was updated successfully, but these errors were encountered: