With any recent version of puppetlabs-apache, in manifests/vhost.pp there is this section of code:
if $wsgi_daemon_process_options {
deprecation('apache::vhost::wsgi_daemon_process_options', 'This parameter is deprecated. Please add values inside Hash `wsgi_daemon_process`.')
}
This triggers a (huge) deprecation warning log message in the puppetserver.log.
The intent seems to be to switch from using the related wsgi_daemon_process option as a string, and instead make it a Hash, likely with the key/value pairs that were being passed in wsgi_daemon_process_options.
The problem is that the documentation doesn't reflect the deprecation. The reference documentation only shows the deprecated usage, not the preferred usage.
Without updated documentation, it's not clear how the String that was the argument to the deprecated use of wsgi_daemon_process is supposed to be incorporated into preferred format Hash.
With any recent version of
puppetlabs-apache, inmanifests/vhost.ppthere is this section of code:This triggers a (huge) deprecation warning log message in the puppetserver.log.
The intent seems to be to switch from using the related
wsgi_daemon_processoption as a string, and instead make it a Hash, likely with the key/value pairs that were being passed inwsgi_daemon_process_options.The problem is that the documentation doesn't reflect the deprecation. The reference documentation only shows the deprecated usage, not the preferred usage.
Without updated documentation, it's not clear how the String that was the argument to the deprecated use of
wsgi_daemon_processis supposed to be incorporated into preferred format Hash.