ec-policy-debugging

Debug Enterprise Contract policy violations by examining METADATA blocks for title, description, and solution, accessing associated tests to verify expected behavior, and correlating attestation data to contextualize failures.

An EC policy violation code identifies a specific rule failure. Find the root cause by inspecting the rule's METADATA block for semantic context, reviewing tests for expected inputs, and analyzing actual attestation data.

Use attestations and SBOMs to diagnose EC policy failures by correlating the actual data within them against the specific policy rules that triggered the violation, helping to pinpoint mismatches and craft remediation steps.

Yes, you can review associated tests and example data to determine expected inputs and identify edge cases, which helps verify rule behavior and accurately diagnose why an Enterprise Contract policy violation occurred.

The best way to fix Enterprise Contract policy violations is to examine the rule's METADATA block for the solution field, verify expected behavior against tests, and correlate attestation data to craft actionable remediation steps.