Need to merge two access policies established through the visual policy editor.

To be clear, we don't recommend people move away from iRules. 

We recommend people make excellent access policies with all the options and choose where to apply them (on what vip). A single vip should not have to go that deep (iRules) most of the time, when an access policy can include all scenarios.

I would recommend you break your policies into macros as much as possible to make them easier to manage.. and migrate. So for this.. make macros for your smaller policies and have them branch off the main policy.

Thanks for the reply Aubrey. As a user, I find orienting on best practices before getting in too deep helps.

Though I am currently being directed to discard infrastructure as code (IaC), I favor an IaC approach over the visual policy editor.  So I have been examining the tooling around setting up the F5 BIG-IP. There are a lot of solutions using Ansible to set-up the load balancer. Then there is the current discussion of using a declarative model vs using an imperative model. It's my understanding that F5 is creating a movement toward the declarative model through tooling such as the application services 3 (AS3) extension whereas historically it has been an imperative model. If you have time, I would love to hear your opinion on this.