Any change in /Common partition removes GSLB topology record configuration from other partitions about f5-appsvcs-extension HOT 4 CLOSED

Possible duplicate issue of AUTOTOOL-4135 where we are performing  'delete gtm topology all' -- Assigning to myself

from f5-appsvcs-extension.

Seems simular issue to AUTOTOOL-4135

• One starts by posting GSLB Topology is Common and wipes it out by posting a non-Common Tenant
• The other starts by posting GSLB Topology in a non-Common Tenant and wipes it out by posting to Common

from f5-appsvcs-extension.

@mdditt2000 - also just noticed that any change in ANY another partition wipes the topology data for every other partition. So basically using Class: GSLB_Topology_Records is broken unless you are in /Common. As I said, my pools are all in separate partitions and applications though, so to move GSLB_Topology_Records to /Common, I'd also have to move all GSLB_Pool configuration to /Common which breaks my partitioning security design.

The only way I can get this to work is if I already create all the GSLB pools in the other tenants/partitions and load them into AS3. Then I can reference them in a separate /Common declaration using the "bigip" selector rather than the "use" selector. Problem with this is that there is stuff in /Common which the other tenants/partitions use - so it ends up a chicken and egg problem. I guess I could use a PATCH to add the topology records afterwards, but I want to avoid PATCH if I can.

from f5-appsvcs-extension.

Thi has been done in AS3 50 release which is planned to release at the end of March, please reach out to us if an early build is required.

from f5-appsvcs-extension.