Forum Discussion
ng_export with Per Request Policies
- Jan 30, 2020
You can already do it with normal policies, no reverse engineering needed.
However that ID 755148 refers to API Protection policies. These are the same as PRPs, but they have a different "type" (I'm sure you noticed already).
The other thing is:
The way I do this usually when I'm creating labs or other material is to walk the configuration hirearchy (policy items, agents, policy, profile, customization groups) and then turn it into a pile of TMSH commands, then use the commands to create a policy. It's kind of fragile between versions, but mostly works fine.
Much to my surprise ng_export is just a php script. reading its contents it doesn't look like support for per-request policies was ever added.
My next option is to try and reverse engineer the GUI / HTTP calls to support programmatic access to the import/export function.
I don't think there is a REST equivalent for profile import/export 😥
If only RFE 755148 could be delivered soon....
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com