The ability for ComplianceRule objects to be based on what is set in network_driver and not based on the single platform that is applied. So, in theory I can have a platform called "Cisco IOS" and one called "Cisco IOSXE", that both have the network_driver of cisco_ios, which should be what we join on vs the platform/platform id.
Use Case
Currently you only have to set network_driver for all other relevant places in order for the feature to work, this use case is different.
Environment
Proposed Functionality
The ability for ComplianceRule objects to be based on what is set in network_driver and not based on the single platform that is applied. So, in theory I can have a platform called "Cisco IOS" and one called "Cisco IOSXE", that both have the network_driver of
cisco_ios, which should be what we join on vs the platform/platform id.Use Case
Currently you only have to set network_driver for all other relevant places in order for the feature to work, this use case is different.