Requestctl has been created as a pure cli tool, which means that a lot of the business logic is currently encapsulated by the cli.Requestctl class.

In order to be able to have a web interface to requestctl, we need to extract a good part of that business logic to an api class that can be used even when not on cli.

This Api class(es) should allow to do the following:

• CRUD operations on any requestctl object, with validation
• Parsing and validation of requestctl expressions
• Search requestctl actions for specific patterns/ipblocks
• Search for specific patterns/ipblocks based on their content
• Generate vcl and haproxy dsl for a specific action
• Commit changes