NAP WAF: Remove CAPTCHA items from declarative policy pages

[aknot242]

Describe the bug

It has been reported that alarm-and-captcha is not a supported action for loginAttemptsFromTheSameIp and loginAttemptsFromTheSameUser features appearing in the declarative policy page for NAP WAF (v4 here, v5 here). If they aren't supported, they should be removed from the documentation.

[ADubhlaoich]

Closing this issue due to the scope:

The policy parameter reference is generated by the engineering team as part of release processes.

The issue should be reported directly to them so they can identify why it's still being included at source time: the alternative is manual intervention with every release to edit automatically generated HTML, which is unsustainable.

[aknot242]

@ADubhlaoich - isn't this where we report documentation issues regardless of who (or what team) can fix them? Can we please re-open this and ask someone from that team to work on it? I can help.

[ADubhlaoich]

Yes, but WAF engineering does not work in GitHub or look at GitHub issues.

A ticket should be filed on their internal engineering board, which is why I suggested reporting it to them directly.

[ADubhlaoich]

Future context notes for issue archaeology:

We have a note under the policy configuration page's Configuration overview section about this file.

F5 WAF for NGINX provides a JSON Schema which can be used to validate a JSON policy file for format compliance.
The schema file can be generated using a script once F5 WAF for NGINX is installed: sudo /opt/app_protect/bin/generate_json_schema.pl.
This script will output the schema to a file named policy.json into the current working directory. Once the schema file is generated, you can use validation tools such as AJV to validate a JSON policy file.
This schema is used for the Policy parameter reference.

I have started a conversation with docs engineering about generating a better-looking reference page using the JSON file instead of committing a HTML file (cc @nginx-jack ), but it does not solve the information being inaccurate at source.

[JTorreG]

Closing this ticket. This is not actionable in this repository and the appropriate team has been notified.