Import irules that have different content but same name

I just asked a similar question to support. This behaviour in BIG-IQ CM seems completely unsuited to real world deployments.

There are two main scenarios where objects with the same name legitimately should have different configuration on different appliances:

• In production where the object refers to a resource in a datacentre (e.g. pool members local to the region) and you want to be able to have other objects (e.g. a VS) be consistently configured in all locations - including pool name references.

   

• Where an application release is graduating through development and test environments (or parallel development environments working on different releases) and the configuration change should not prematurely be deployed to other environments.

   

Due to this, and the way CM gives quite a limited range of configuration compared to BIG-IP, I can't see us using CM for configuration deployment at all.