You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
--simulate-json: optionally include manifest-full's unchanged (kept) files #31
--simulate-json writes only the change set. --simulate=manifest-full additionally lists files the policy touched and found already compliant, read from CHROOT_KEPT_LIST_FILE. That list is available when the JSON is written, so it can be added. This was a scope choice, not a technical limit.
Cost and design questions:
About 20–30 lines.
Each kept file needs a SHA-256, and there could be many.
A separate unchanged array, or "change": "unchanged" entries mixed into files? The separate array keeps "every entry in files is a change" true.
First, check whether tendcf needs this. For example, does its approval or audit flow need to see what the policy verified, not only what it would change? If not, leave it until someone upstream asks.
Activity