[Bug]: F5-WAF VM/Bare Metal installation fails due to incorrect directive

[aknot242]

Describe the bug you have identified

In the [VM/Bare Metal installation doc], there is a configuration step that asks you to use a directive that will cause the following failure on NGINX start/reload:

nginx: [emerg] APP_PROTECT config_set_id 1760459488-666-81448 not found within 45 seconds
nginx: [emerg] APP_PROTECT fstat() "/opt/app_protect/config/compile_error_msg.json" failed (2: No such file or directory)
nginx: configuration file /etc/nginx/nginx.conf test failed

The app_protect_enforcer_address directive should only be used in the containerized packaging of F5 WAF.

Which product or products does this request relate to?

F5 WAF for NGINX

Steps to reproduce the bug

1. Follow the installation instructions contained in the VM/Bare Metal docs, including the configuration section steps.
2. Restart NGINX, and the error message will appear.

What is the expected or desired behaviour?

NGINX and WAF should start successfully.

What environments or versions does this bug affect?

All VM or Bare Metal package-based deployments.

Any additional information

No response

[aknot242]

This is going to be a little more effort to resolve, as the waf/install-update-configuration.md seems to be used in the docker.md, kubernetes.md and virtual-environment.md files. The first two should use this directive, but the last should not.

[JTorreG]

If I am understanding the comment correctly, we need a new include (or not use one) for virtual-environment, removing the directive mentioned above