3.5. iApp/Policy Redeployment BehaviourΒΆ

The App Services Integration iApp template includes the ability to control what action is taken with policies upon an iApp re-deployment event. This functionality applies specifically to ASM and APM policies and controls two specific categories of behaviour:

  1. The action the template will take with the policy object upon re-deployment. This action controls whether the source-of-truth for the policy is the current config on the BIG-IP device or the policy bundled/loaded in the template.
    • preserve: The policy on the device will be preserved. This option allows direct policy manipulation on the device or by third party systems
    • redeploy: The policy bundled in the template will be re-deployed, overwriting any local changes
  2. Whether user traffic is allowed through the virtual server during re-deployment
    • bypass: User traffic will bypass all policies during redeployment
    • block: The virtual server will be marked down resulting in no user traffic transiting the virtual server

The available options are:

Option Name Description
preserve-bypass
  • Source-of-truth: BIG-IP Device
  • Traffic: Allowed during re-deployment
preserve-block
  • Source-of-truth: BIG-IP Device
  • Traffic: Blocked during re-deployment
redeploy-bypass
  • Source-of-truth: iApp template
  • Traffic: Allowed during re-deployment
redeploy-block
  • Source-of-truth: iApp template
  • Traffic: Blocked during re-deployment

The behaviour can be controlled independently using these fields:

The BIG-IP API Reference documentation contains community-contributed content. F5 does not monitor or control community code contributions. We make no guarantees or warranties regarding the available code, and it may contain errors, defects, bugs, inaccuracies, or security vulnerabilities. Your access to and use of any code available in the BIG-IP API reference guides is solely at your own risk.