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
Affected Puppet, Ruby, OS and module versions/distributions
Puppet: Any
Ruby: Any
Distribution: Any
Module version: Any
Any additional information you'd like to impart
Currently, access_log can only be directly defined in the server scope. (Re)defining at location scope requires location_cfg_append or, in our case, raw_append.
Since we use multiple access_log statements at various levels of the configuration, this is difficult to maintain. The suggested (in resource/location.pp) way to define access_log for a location - using location_cfg_append - cannot be used since we need more than one entry. As a result, we are required to use raw_append or similar instead. This in turn leads to other problems; we cannot "inherit" the access_log statements from the server level, since those are defined as arrays.
While I'm sure there are ways around this, so we can define a common set of access_log settings in one place and re-use - for example by using raw_prepend/append also on the server level, this feels clumsy.
Support for access_log (and error_log) on all levels - http, server, location (and possibly 'if' and 'limit_except') - would be quite helpful.
Thanks for reading!
The text was updated successfully, but these errors were encountered:
Affected Puppet, Ruby, OS and module versions/distributions
Any additional information you'd like to impart
Currently,
access_log
can only be directly defined in the server scope. (Re)defining at location scope requireslocation_cfg_append
or, in our case,raw_append
.Since we use multiple access_log statements at various levels of the configuration, this is difficult to maintain. The suggested (in resource/location.pp) way to define access_log for a location - using location_cfg_append - cannot be used since we need more than one entry. As a result, we are required to use raw_append or similar instead. This in turn leads to other problems; we cannot "inherit" the access_log statements from the server level, since those are defined as arrays.
While I'm sure there are ways around this, so we can define a common set of access_log settings in one place and re-use - for example by using raw_prepend/append also on the server level, this feels clumsy.
Support for access_log (and error_log) on all levels - http, server, location (and possibly 'if' and 'limit_except') - would be quite helpful.
Thanks for reading!
The text was updated successfully, but these errors were encountered: