You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The validation added in #634 appears to have broken the ability to configure the PM settings via environment variables (interpreted at runtime), which is something we do to allow our environment to determine the PHP runtime settings.
Suggestion would be to make these either Variant[String, Integer[..]] or for a more strict approach something like, Variant[Pattern[/\$\{[\w]+\}/], Integer[..]].
What behaviour did you expect instead
No Puppet errors, environment variable based configuration written out to file.
Output log
Error: Evaluation Error: Error while evaluating a Resource Statement, Php::Fpm::Pool[www]:
parameter 'pm_max_children' expects an Integer value, got String
parameter 'pm_start_servers' expects an Integer value, got String
parameter 'pm_min_spare_servers' expects an Integer value, got String
parameter 'pm_max_spare_servers' expects an Integer value, got String
parameter 'pm_max_requests' expects an Integer value, got String
The text was updated successfully, but these errors were encountered:
chrisboulton
added a commit
to chrisboulton/puppet-php
that referenced
this issue
Jan 5, 2022
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
The validation added in #634 appears to have broken the ability to configure the PM settings via environment variables (interpreted at runtime), which is something we do to allow our environment to determine the PHP runtime settings.
Per the PHP docs, this is a supported configuration: https://www.php.net/manual/en/configuration.file.php#example-1
Suggestion would be to make these either
Variant[String, Integer[..]]
or for a more strict approach something like,Variant[Pattern[/\$\{[\w]+\}/], Integer[..]]
.What behaviour did you expect instead
No Puppet errors, environment variable based configuration written out to file.
Output log
The text was updated successfully, but these errors were encountered: