Actions38
- APM Actions
- ASM Actions
- Authentication Actions
- LTM Actions
- System Actions
ASM → Diff Policies
AI-generatedSummary
Starts an ASM policy-diff background task on a BIG-IP by POSTing two policy self-links to /mgmt/tm/asm/tasks/policy-diff, so the differences between the two WAF policies can be computed.
Inputs
- First Policy Link (required) — Self-link of the first ASM policy to compare, e.g. https://localhost/mgmt/tm/asm/policies/example_1. Sent as firstPolicyReference: {link: ...}.
- Second Policy Link (required) — Self-link of the second ASM policy to compare. Sent as secondPolicyReference: {link: ...}.
- Request Options — Node settings for the HTTP request: batching (items per batch, default 50, and interval in ms, default 1000), ignore SSL certificate issues, an HTTP proxy, and a timeout in ms (default 10000).
Output shape
The JSON response from the BIG-IP for the created policy-diff task, returned as the node's output item(s).
The source does not process the response. The diff is a task, so the response is the task object and not necessarily the finished diff. Use the Merge Policies operation (which takes a policy-diff reference link) to act on the result. The Check Task Status operation does not list policy-diff as a task type. Authentication uses the bigIpF5Api credential.
Examples
Example 1: Compare a staging WAF policy with the production one before promoting changes.
Resource: ASM; Operation: Diff Policies; First Policy Link: https://localhost/mgmt/tm/asm/policies/
Example 2: Run the diff against a BIG-IP with a self-signed certificate.
Set both policy links, then add Request Options > Ignore SSL Issues (Insecure) = true.