apache::mod::proxy_balancer default configuration with custom parameters $manager => true, $allow_from => ['10.10.10.10','11.11.11.11'], $status_path => '/custom-manager' on a Debian OS is expected to contain File[proxy_balancer.conf] with content supplied string Failure/Error: expect(subject).to contain_file('proxy_balancer.conf').with_content(expected) Puppet::PreformattedError: Evaluation Error: Error while evaluating a Function Call, Could not find template 'apache/mod/status.conf.erb' (file: /home/runner/work/puppetlabs-apache/puppetlabs-apache/spec/fixtures/modules/apache/manifests/mod/status.pp, line: 47, column: 16) on node fv-az882-706.q2gudnguzteuze5zk335zrm3jf.ex.internal.cloudapp.net

apache::mod::security on centos-7-x86_64 on RedHat based systems with CRS parameters is expected to contain File[/etc/httpd/modsecurity.d/security_crs.conf] with content =~ / ^SecAction\ \\\n \ \ "id:'900001',\ \\\n \ \ phase:1,\ \\\n \ \ t:none,\ \\\n \ \ setvar:tx.critical_anomaly_score=5,\ \\\n \ \ setvar:tx.error_anomaly_score=4,\ \\\n \ \ setvar:tx.warning_anomaly_score=3,\ \\\n \ \ setvar:tx.notice_anomaly_score=2,\ \\\n \ \ nolog,\ \\\n \ \ pass"$ /x Failure/Error: expect(subject).to contain_file('/etc/httpd/modsecurity.d/security_crs.conf').with_content \ %r{ ^SecAction\ \\\n \ \ "id:'900001',\ \\\n \ \ phase:1,\ \\\n \ \ t:none,\ \\\n \ \ setvar:tx.critical_anomaly_score=5,\ \\\n \ \ setvar:tx.error_anomaly_score=4,\ \\\n \ \ setvar:tx.warning_anomaly_score=3,\ \\\n \ \ setvar:tx.notice_anomaly_score=2,\ \\\n expected that the catalogue would contain File[/etc/httpd/modsecurity.d/security_crs.conf] with content set to / ^SecAction\ \\\n \ \ "id:'900001',\ \\\n \ \ phase:1,\ \\\n \ \ t:none,\ \\\n \ \ setvar:tx.critical_anomaly_score=5,\ \\\n \ \ setvar:tx.error_anomaly_score=4,\ \\\n \ \ setvar:tx.warning_anomaly_score=3,\ \\\n \ \ setvar:tx.notice_anomaly_score=2,\ \\\n \ \ nolog,\ \\\n \ \ pass"$ /x but it is set to "# ------------------------------------------------------------------------\n# OWASP ModSecurity Core Rule Set ver.3.3.2\n# Copyright (c) 2006-2020 Trustwave and contributors. All rights reserved.\n#\n# The OWASP ModSecurity Core Rule Set is distributed under\n# Apache Software License (ASL) version 2\n# Please see the enclosed LICENSE file for full details.\n# ------------------------------------------------------------------------\n\n\n#\n# -- [[ Introduction ]] --------------------------------------------------------\n#\n# The OWASP ModSecurity Core Rule Set (CRS) is a set of generic attack\n# detection rules that provide a base level of protection for any web\n# application. They are written for the open source, cross-platform\n# ModSecurity Web Application Firewall.\n#\n# See also:\n# https://coreruleset.org/\n# https://github.com/SpiderLabs/owasp-modsecurity-crs\n# https://www.owasp.org/index.php/Category:OWASP_ModSecurity_Core_Rule_Set_Project\n#\n\n\n#\n# -- [[ System Requirements ]] -------------------------------------------------\n#\n# CRS requires ModSecurity version 2.8.0 or above.\n# We recommend to always use the newest ModSecurity version.\n#\n# The configuration directives/settings in this file are used to control\n# the OWASP ModSecurity CRS. These settings do **NOT** configure the main\n# ModSecurity settings (modsecurity.conf) such as SecRuleEngine,\n# SecRequestBodyAccess, SecAuditEngine, SecDebugLog, and XML processing.\n#\n# The CRS assumes that modsecurity.conf has been loaded. It is bundled with\n# ModSecurity. If you don't have it, you can get it from:\n# 2.x: https://raw.githubusercontent.com/SpiderLabs/ModSecurity/v2/master/modsecurity.conf-recommended\n# 3.x: https://raw.githubusercontent.com/SpiderLabs/ModSecurity/v3/master/modsecurity.conf-recommended\n#\n# The order of file inclusion in your webserver configuration should always be:\n# 1. modsecurity.conf\n# 2. crs-setup.conf (this file)\n# 3. rules/*.conf (the CRS rule files)\n#\n# Please refer to the INSTALL file for detailed installation instructions.\n#\n\n\n#\n# -- [[ Mode of Operation: Anomaly Scoring vs. Self-Contained ]] ---------------\n#\n# The CRS can run in two modes:\n#\n# -- [[ Anomaly Scoring Mode (default) ]] --\n# In CRS3, anomaly mode is the default and recommended mode, since it gives the\n# most

apache::mod::security on oraclelinux-7-x86_64 on RedHat based systems with CRS parameters is expected to contain File[/etc/httpd/modsecurity.d/security_crs.conf] with content =~ / ^SecAction\ \\\n \ \ "id:'900001',\ \\\n \ \ phase:1,\ \\\n \ \ t:none,\ \\\n \ \ setvar:tx.critical_anomaly_score=5,\ \\\n \ \ setvar:tx.error_anomaly_score=4,\ \\\n \ \ setvar:tx.warning_anomaly_score=3,\ \\\n \ \ setvar:tx.notice_anomaly_score=2,\ \\\n \ \ nolog,\ \\\n \ \ pass"$ /x Failure/Error: expect(subject).to contain_file('/etc/httpd/modsecurity.d/security_crs.conf').with_content \ %r{ ^SecAction\ \\\n \ \ "id:'900001',\ \\\n \ \ phase:1,\ \\\n \ \ t:none,\ \\\n \ \ setvar:tx.critical_anomaly_score=5,\ \\\n \ \ setvar:tx.error_anomaly_score=4,\ \\\n \ \ setvar:tx.warning_anomaly_score=3,\ \\\n \ \ setvar:tx.notice_anomaly_score=2,\ \\\n expected that the catalogue would contain File[/etc/httpd/modsecurity.d/security_crs.conf] with content set to / ^SecAction\ \\\n \ \ "id:'900001',\ \\\n \ \ phase:1,\ \\\n \ \ t:none,\ \\\n \ \ setvar:tx.critical_anomaly_score=5,\ \\\n \ \ setvar:tx.error_anomaly_score=4,\ \\\n \ \ setvar:tx.warning_anomaly_score=3,\ \\\n \ \ setvar:tx.notice_anomaly_score=2,\ \\\n \ \ nolog,\ \\\n \ \ pass"$ /x but it is set to "# ------------------------------------------------------------------------\n# OWASP ModSecurity Core Rule Set ver.3.3.2\n# Copyright (c) 2006-2020 Trustwave and contributors. All rights reserved.\n#\n# The OWASP ModSecurity Core Rule Set is distributed under\n# Apache Software License (ASL) version 2\n# Please see the enclosed LICENSE file for full details.\n# ------------------------------------------------------------------------\n\n\n#\n# -- [[ Introduction ]] --------------------------------------------------------\n#\n# The OWASP ModSecurity Core Rule Set (CRS) is a set of generic attack\n# detection rules that provide a base level of protection for any web\n# application. They are written for the open source, cross-platform\n# ModSecurity Web Application Firewall.\n#\n# See also:\n# https://coreruleset.org/\n# https://github.com/SpiderLabs/owasp-modsecurity-crs\n# https://www.owasp.org/index.php/Category:OWASP_ModSecurity_Core_Rule_Set_Project\n#\n\n\n#\n# -- [[ System Requirements ]] -------------------------------------------------\n#\n# CRS requires ModSecurity version 2.8.0 or above.\n# We recommend to always use the newest ModSecurity version.\n#\n# The configuration directives/settings in this file are used to control\n# the OWASP ModSecurity CRS. These settings do **NOT** configure the main\n# ModSecurity settings (modsecurity.conf) such as SecRuleEngine,\n# SecRequestBodyAccess, SecAuditEngine, SecDebugLog, and XML processing.\n#\n# The CRS assumes that modsecurity.conf has been loaded. It is bundled with\n# ModSecurity. If you don't have it, you can get it from:\n# 2.x: https://raw.githubusercontent.com/SpiderLabs/ModSecurity/v2/master/modsecurity.conf-recommended\n# 3.x: https://raw.githubusercontent.com/SpiderLabs/ModSecurity/v3/master/modsecurity.conf-recommended\n#\n# The order of file inclusion in your webserver configuration should always be:\n# 1. modsecurity.conf\n# 2. crs-setup.conf (this file)\n# 3. rules/*.conf (the CRS rule files)\n#\n# Please refer to the INSTALL file for detailed installation instructions.\n#\n\n\n#\n# -- [[ Mode of Operation: Anomaly Scoring vs. Self-Contained ]] ---------------\n#\n# The CRS can run in two modes:\n#\n# -- [[ Anomaly Scoring Mode (default) ]] --\n# In CRS3, anomaly mode is the default and recommended mode, since it gives the\n#

apache::mod::security on redhat-7-x86_64 on RedHat based systems with CRS parameters is expected to contain File[/etc/httpd/modsecurity.d/security_crs.conf] with content =~ / ^SecAction\ \\\n \ \ "id:'900001',\ \\\n \ \ phase:1,\ \\\n \ \ t:none,\ \\\n \ \ setvar:tx.critical_anomaly_score=5,\ \\\n \ \ setvar:tx.error_anomaly_score=4,\ \\\n \ \ setvar:tx.warning_anomaly_score=3,\ \\\n \ \ setvar:tx.notice_anomaly_score=2,\ \\\n \ \ nolog,\ \\\n \ \ pass"$ /x Failure/Error: expect(subject).to contain_file('/etc/httpd/modsecurity.d/security_crs.conf').with_content \ %r{ ^SecAction\ \\\n \ \ "id:'900001',\ \\\n \ \ phase:1,\ \\\n \ \ t:none,\ \\\n \ \ setvar:tx.critical_anomaly_score=5,\ \\\n \ \ setvar:tx.error_anomaly_score=4,\ \\\n \ \ setvar:tx.warning_anomaly_score=3,\ \\\n \ \ setvar:tx.notice_anomaly_score=2,\ \\\n expected that the catalogue would contain File[/etc/httpd/modsecurity.d/security_crs.conf] with content set to / ^SecAction\ \\\n \ \ "id:'900001',\ \\\n \ \ phase:1,\ \\\n \ \ t:none,\ \\\n \ \ setvar:tx.critical_anomaly_score=5,\ \\\n \ \ setvar:tx.error_anomaly_score=4,\ \\\n \ \ setvar:tx.warning_anomaly_score=3,\ \\\n \ \ setvar:tx.notice_anomaly_score=2,\ \\\n \ \ nolog,\ \\\n \ \ pass"$ /x but it is set to "# ------------------------------------------------------------------------\n# OWASP ModSecurity Core Rule Set ver.3.3.2\n# Copyright (c) 2006-2020 Trustwave and contributors. All rights reserved.\n#\n# The OWASP ModSecurity Core Rule Set is distributed under\n# Apache Software License (ASL) version 2\n# Please see the enclosed LICENSE file for full details.\n# ------------------------------------------------------------------------\n\n\n#\n# -- [[ Introduction ]] --------------------------------------------------------\n#\n# The OWASP ModSecurity Core Rule Set (CRS) is a set of generic attack\n# detection rules that provide a base level of protection for any web\n# application. They are written for the open source, cross-platform\n# ModSecurity Web Application Firewall.\n#\n# See also:\n# https://coreruleset.org/\n# https://github.com/SpiderLabs/owasp-modsecurity-crs\n# https://www.owasp.org/index.php/Category:OWASP_ModSecurity_Core_Rule_Set_Project\n#\n\n\n#\n# -- [[ System Requirements ]] -------------------------------------------------\n#\n# CRS requires ModSecurity version 2.8.0 or above.\n# We recommend to always use the newest ModSecurity version.\n#\n# The configuration directives/settings in this file are used to control\n# the OWASP ModSecurity CRS. These settings do **NOT** configure the main\n# ModSecurity settings (modsecurity.conf) such as SecRuleEngine,\n# SecRequestBodyAccess, SecAuditEngine, SecDebugLog, and XML processing.\n#\n# The CRS assumes that modsecurity.conf has been loaded. It is bundled with\n# ModSecurity. If you don't have it, you can get it from:\n# 2.x: https://raw.githubusercontent.com/SpiderLabs/ModSecurity/v2/master/modsecurity.conf-recommended\n# 3.x: https://raw.githubusercontent.com/SpiderLabs/ModSecurity/v3/master/modsecurity.conf-recommended\n#\n# The order of file inclusion in your webserver configuration should always be:\n# 1. modsecurity.conf\n# 2. crs-setup.conf (this file)\n# 3. rules/*.conf (the CRS rule files)\n#\n# Please refer to the INSTALL file for detailed installation instructions.\n#\n\n\n#\n# -- [[ Mode of Operation: Anomaly Scoring vs. Self-Contained ]] ---------------\n#\n# The CRS can run in two modes:\n#\n# -- [[ Anomaly Scoring Mode (default) ]] --\n# In CRS3, anomaly mode is the default and recommended mode, since it gives the\n# most

apache::mod::security on scientific-7-x86_64 on RedHat based systems with CRS parameters is expected to contain File[/etc/httpd/modsecurity.d/security_crs.conf] with content =~ / ^SecAction\ \\\n \ \ "id:'900001',\ \\\n \ \ phase:1,\ \\\n \ \ t:none,\ \\\n \ \ setvar:tx.critical_anomaly_score=5,\ \\\n \ \ setvar:tx.error_anomaly_score=4,\ \\\n \ \ setvar:tx.warning_anomaly_score=3,\ \\\n \ \ setvar:tx.notice_anomaly_score=2,\ \\\n \ \ nolog,\ \\\n \ \ pass"$ /x Failure/Error: expect(subject).to contain_file('/etc/httpd/modsecurity.d/security_crs.conf').with_content \ %r{ ^SecAction\ \\\n \ \ "id:'900001',\ \\\n \ \ phase:1,\ \\\n \ \ t:none,\ \\\n \ \ setvar:tx.critical_anomaly_score=5,\ \\\n \ \ setvar:tx.error_anomaly_score=4,\ \\\n \ \ setvar:tx.warning_anomaly_score=3,\ \\\n \ \ setvar:tx.notice_anomaly_score=2,\ \\\n expected that the catalogue would contain File[/etc/httpd/modsecurity.d/security_crs.conf] with content set to / ^SecAction\ \\\n \ \ "id:'900001',\ \\\n \ \ phase:1,\ \\\n \ \ t:none,\ \\\n \ \ setvar:tx.critical_anomaly_score=5,\ \\\n \ \ setvar:tx.error_anomaly_score=4,\ \\\n \ \ setvar:tx.warning_anomaly_score=3,\ \\\n \ \ setvar:tx.notice_anomaly_score=2,\ \\\n \ \ nolog,\ \\\n \ \ pass"$ /x but it is set to "# ------------------------------------------------------------------------\n# OWASP ModSecurity Core Rule Set ver.3.3.2\n# Copyright (c) 2006-2020 Trustwave and contributors. All rights reserved.\n#\n# The OWASP ModSecurity Core Rule Set is distributed under\n# Apache Software License (ASL) version 2\n# Please see the enclosed LICENSE file for full details.\n# ------------------------------------------------------------------------\n\n\n#\n# -- [[ Introduction ]] --------------------------------------------------------\n#\n# The OWASP ModSecurity Core Rule Set (CRS) is a set of generic attack\n# detection rules that provide a base level of protection for any web\n# application. They are written for the open source, cross-platform\n# ModSecurity Web Application Firewall.\n#\n# See also:\n# https://coreruleset.org/\n# https://github.com/SpiderLabs/owasp-modsecurity-crs\n# https://www.owasp.org/index.php/Category:OWASP_ModSecurity_Core_Rule_Set_Project\n#\n\n\n#\n# -- [[ System Requirements ]] -------------------------------------------------\n#\n# CRS requires ModSecurity version 2.8.0 or above.\n# We recommend to always use the newest ModSecurity version.\n#\n# The configuration directives/settings in this file are used to control\n# the OWASP ModSecurity CRS. These settings do **NOT** configure the main\n# ModSecurity settings (modsecurity.conf) such as SecRuleEngine,\n# SecRequestBodyAccess, SecAuditEngine, SecDebugLog, and XML processing.\n#\n# The CRS assumes that modsecurity.conf has been loaded. It is bundled with\n# ModSecurity. If you don't have it, you can get it from:\n# 2.x: https://raw.githubusercontent.com/SpiderLabs/ModSecurity/v2/master/modsecurity.conf-recommended\n# 3.x: https://raw.githubusercontent.com/SpiderLabs/ModSecurity/v3/master/modsecurity.conf-recommended\n#\n# The order of file inclusion in your webserver configuration should always be:\n# 1. modsecurity.conf\n# 2. crs-setup.conf (this file)\n# 3. rules/*.conf (the CRS rule files)\n#\n# Please refer to the INSTALL file for detailed installation instructions.\n#\n\n\n#\n# -- [[ Mode of Operation: Anomaly Scoring vs. Self-Contained ]] ---------------\n#\n# The CRS can run in two modes:\n#\n# -- [[ Anomaly Scoring Mode (default) ]] --\n# In CRS3, anomaly mode is the default and recommended mode, since it gives the\n#

apache::mod::status default configuration with parameters on a Debian 11 OS with default params is expected to contain Apache::Mod[status] Failure/Error: it { is_expected.to contain_apache__mod('status') } Puppet::PreformattedError: Evaluation Error: Error while evaluating a Function Call, Could not find template 'apache/mod/status.conf.erb' (file: /home/runner/work/puppetlabs-apache/puppetlabs-apache/spec/fixtures/modules/apache/manifests/mod/status.pp, line: 47, column: 16) on node fv-az882-706.q2gudnguzteuze5zk335zrm3jf.ex.internal.cloudapp.net

apache::mod::status default configuration with parameters on a Debian 11 OS with default params status conf require Failure/Error: expect(subject).to contain_file('status.conf').with_content(expected) Puppet::PreformattedError: Evaluation Error: Error while evaluating a Function Call, Could not find template 'apache/mod/status.conf.erb' (file: /home/runner/work/puppetlabs-apache/puppetlabs-apache/spec/fixtures/modules/apache/manifests/mod/status.pp, line: 47, column: 16) on node fv-az882-706.q2gudnguzteuze5zk335zrm3jf.ex.internal.cloudapp.net Shared Example Group: "status_conf_spec_require" called from ./spec/classes/mod/status_spec.rb:56

apache::mod::status default configuration with parameters on a Debian 11 OS with default params is expected to contain File[status.conf] with ensure => "file" and path => "/etc/apache2/mods-available/status.conf" Failure/Error: expect(subject).to contain_file('status.conf').with(ensure: 'file', path: '/etc/apache2/mods-available/status.conf') Puppet::PreformattedError: Evaluation Error: Error while evaluating a Function Call, Could not find template 'apache/mod/status.conf.erb' (file: /home/runner/work/puppetlabs-apache/puppetlabs-apache/spec/fixtures/modules/apache/manifests/mod/status.pp, line: 47, column: 16) on node fv-az882-706.q2gudnguzteuze5zk335zrm3jf.ex.internal.cloudapp.net

apache::mod::status default configuration with parameters on a Debian 11 OS with default params is expected to contain File[status.conf symlink] with ensure => "link" and path => "/etc/apache2/mods-enabled/status.conf" Failure/Error: expect(subject).to contain_file('status.conf symlink').with(ensure: 'link', path: '/etc/apache2/mods-enabled/status.conf') Puppet::PreformattedError: Evaluation Error: Error while evaluating a Function Call, Could not find template 'apache/mod/status.conf.erb' (file: /home/runner/work/puppetlabs-apache/puppetlabs-apache/spec/fixtures/modules/apache/manifests/mod/status.pp, line: 47, column: 16) on node fv-az882-706.q2gudnguzteuze5zk335zrm3jf.ex.internal.cloudapp.net