Problem
Currently, LUFA's compliance endpoint (/api/v1/compliance/hosts) reports all hosts that are non-compliant with any compliance-related template. In some scenarios, administrators need to temporarily or permanently exclude specific host-template combinations from compliance reporting — for example during maintenance windows, planned deprecations, or known issues that cannot be resolved.
There is no way to exclude a specific host from being reported for a specific template's non-compliance.
Expected Behavior
Administrators should be able to disable (opt-out) compliance checking for a specific template on a specific host directly from the host detail page. When a template-host combination is disabled:
- The host should not appear in the /api/v1/compliance/hosts endpoints for that template.
- The host's overall compliance status (v_host_compliance) should ignore that template.
- The UI should clearly indicate the opt-out state.
Problem
Currently, LUFA's compliance endpoint (/api/v1/compliance/hosts) reports all hosts that are non-compliant with any compliance-related template. In some scenarios, administrators need to temporarily or permanently exclude specific host-template combinations from compliance reporting — for example during maintenance windows, planned deprecations, or known issues that cannot be resolved.
There is no way to exclude a specific host from being reported for a specific template's non-compliance.
Expected Behavior
Administrators should be able to disable (opt-out) compliance checking for a specific template on a specific host directly from the host detail page. When a template-host combination is disabled: