From 9803e857a2868a8ca65abe55e4746074ffbec1d6 Mon Sep 17 00:00:00 2001 From: Mark Bestavros Date: Tue, 15 Aug 2023 10:18:04 -0400 Subject: [PATCH] Allow not-yet-effective successes in output Signed-off-by: Mark Bestavros --- internal/evaluator/conftest_evaluator.go | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/internal/evaluator/conftest_evaluator.go b/internal/evaluator/conftest_evaluator.go index 594e4804f..bac5ac0de 100644 --- a/internal/evaluator/conftest_evaluator.go +++ b/internal/evaluator/conftest_evaluator.go @@ -501,16 +501,6 @@ func (c conftestEvaluator) computeSuccesses(result Outcome, rules policyRules, e // Let's omit the solution text here because if the rule is passing // already then the user probably doesn't care about the solution. - if !isResultEffective(success, effectiveTime) { - log.Debugf("Skipping result success: %#v", success) - continue - } - - // Todo maybe: We could also call isResultEffective here for the - // success and skip it if the rule is not yet effective. This would - // require collecting the effective_on value from the custom annotation - // in rule.RuleInfo. - successes = append(successes, success) }