Skip to content

Replace "Code tampering detected" with a less alarmist message #1752

Description

@st3penta

The trusted_task policy rules emit the message "Code tampering detected" in two scenarios:

  1. When a trusted artifact input was not produced by the pipeline (valid_trusted_artifact_inputs rule in policy/release/trusted_task/trusted_task.rego around line 208)
  2. When an untrusted PipelineTask is found in the build chain (around line 552)

This wording is overly alarming and can cause unnecessary panic for users whose pipelines simply have a configuration issue or include a task not yet on the trusted list.

The message should be replaced with something more accurate and measured, such as "Untrusted task or input detected in build pipeline" or similar.

The corresponding test expectations in trusted_task_test.rego and documentation in release_trusted_task.adoc must also be updated.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions