Protected vs Not-Protected BIG-IP® Connection in Functional Tests

[ssorenso]

In the
./f5-cccl/f5_cccl/resource/ltm/*monitor.py
Set of files, there is a variable that should be protected called *Monitor.monitor_schema_kvps. So in the...

• ./http_monitor.py it is the HTTPMonitor.monitor_schema_kvps
• ./https_monitor.py it is the HTTPSMonitor.monitor_schema_kvps
• ./icmp_monitor.py it is the ICMPMonitor.monitor_schema_kvps
• ./tcp_monitor.py it is the TCPMonitor.monitor_schema_kvps

These objects are namedtuple's that should be only changeable by this object, but share across all instantiated instances. In the way that I originally authored these files, it is modified in the "BEGIN" statement in the bottom of each file within the if/then block for whether or not the executor instance is __main__ (negative) or not (positive).

This was originally meant to be a level of future-proofing allowing for the later functionality of implementing a dynamic schema based upon the original inputs that might include different schemas.

This is a low-priority bug or enhancement that would add a level of protection.