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
Adding some modules to the 'php.modules' pillar results in an incorrectly configured 'pkgs' list for Debian but works on Gentoo.
Modules such as: php7-fileinfo (fileinfo), php7-tokenizer(tokenizer), php7-ctype(ctype).
The error isn't clear and the modules pillar works on some platforms but not others.
Describe the solution you'd like
I would suggest that lookup entries could be added for the relevant packages to the map.jinja file lookup to prevent the pkgs error.
All the above missing modules are included in the php7-common package on Debian so could be simply referenced in the lookup pillar as such.
A similar approach appears to have been taken for Redhat with Curl and Json.
Describe alternatives you've considered
The simplest alternative could be to perhaps just add comment into the example pillar to check against the map.jinja lookup / check if the packages are included in the PHP install. However, this doesn't prevent a pillar that works on one distribution from failing on another distribution.
Is your feature request related to a problem?
Adding some modules to the 'php.modules' pillar results in an incorrectly configured 'pkgs' list for Debian but works on Gentoo.
Modules such as: php7-fileinfo (fileinfo), php7-tokenizer(tokenizer), php7-ctype(ctype).
The error isn't clear and the modules pillar works on some platforms but not others.
Describe the solution you'd like
I would suggest that lookup entries could be added for the relevant packages to the map.jinja file lookup to prevent the pkgs error.
All the above missing modules are included in the php7-common package on Debian so could be simply referenced in the lookup pillar as such.
A similar approach appears to have been taken for Redhat with Curl and Json.
Describe alternatives you've considered
The simplest alternative could be to perhaps just add comment into the example pillar to check against the map.jinja lookup / check if the packages are included in the PHP install. However, this doesn't prevent a pillar that works on one distribution from failing on another distribution.
Additional context
FYI, the section of the map.jinja referenced is:
I would suggest the update could be to add the below to the list:
The text was updated successfully, but these errors were encountered: