Compliance rule mapping to support multi-tenancy

[jmpettit]

Environment

• Python version: current
• Nautobot version: current
• nautobot-golden-config version: current

Proposed Functionality

Extend Compliance Rule mapping to additional fields, ie. tenant, role

Use Case

As a Network Operator in a company with multiple business units using a shared Nautobot deployment we are running into conflicts with Compliance Rules only being mapped to Platform. Our business units have shared platforms (Junos, NX-OS, IOS) but have different opinions on what sections of the config should be used for compliance.

We would like to be able to map compliance rules to additional fields, at the least Tenant, but I can see use cases for expanding it to Role also (Junos SRX firewall vs router/switch, Cisco IOS switch vs wireless access-point).

As we add more business units and move towards full configuration compliance this is going to be even more of problem since any changes to the compliance rules will cause other business units with the same platform to become non-compliant.

@netopsengineer