Skip to content

feat(tkn-bundle-oci-ta): add STEPS_IMAGE_STEP_NAMES#3135

Draft
joejstuart wants to merge 1 commit intoconforma:mainfrom
joejstuart:tkn-bundle-update
Draft

feat(tkn-bundle-oci-ta): add STEPS_IMAGE_STEP_NAMES#3135
joejstuart wants to merge 1 commit intoconforma:mainfrom
joejstuart:tkn-bundle-update

Conversation

@joejstuart
Copy link
Contributor

@joejstuart joejstuart commented Feb 27, 2026

Add STEPS_IMAGE_STEP_NAMES parameter to build-tekton-bundle task in cli-main pull-request and push pipelineRuns. This limits STEPS_IMAGE replacement to steps using quay.io/conforma/cli:latest in verify-conforma-konflux-ta, leaving other task steps unchanged.

https://issues.redhat.com/browse/EC-1685

Assisted-by: Claude Opus 4.6

Add STEPS_IMAGE_STEP_NAMES parameter to build-tekton-bundle task
in cli-main pull-request and push pipelineRuns. This limits
STEPS_IMAGE replacement to steps using quay.io/conforma/cli:latest
in verify-conforma-konflux-ta, leaving other task steps unchanged.

Assisted-by: Claude Opus 4.6
@joejstuart joejstuart marked this pull request as draft February 27, 2026 16:21
@qodo-code-review
Copy link
Contributor

Review Summary by Qodo

Add STEPS_IMAGE_STEP_NAMES parameter to Tekton bundle tasks

✨ Enhancement

Grey Divider

Walkthroughs

Description
• Add STEPS_IMAGE_STEP_NAMES parameter to build-tekton-bundle task
• Limits image replacement to specific steps in verify-conforma-konflux-ta
• Update tkn-bundle-oci-ta task reference from 0.2 to 0.3
• Apply changes consistently across pull-request and push pipelines
Diagram
flowchart LR
  A["build-tekton-bundle task"] -- "adds STEPS_IMAGE_STEP_NAMES parameter" --> B["Selective image replacement"]
  A -- "updates task version" --> C["tkn-bundle-oci-ta:0.3"]
  B -- "targets specific steps" --> D["verify-conforma-konflux-ta"]
Loading

Grey Divider

File Changes

1. .tekton/cli-main-pull-request.yaml ✨ Enhancement +4/-1

Add STEPS_IMAGE_STEP_NAMES to pull-request pipeline

• Add STEPS_IMAGE_STEP_NAMES parameter with !use-trusted-artifact value
• Update tkn-bundle-oci-ta task reference from version 0.2 to 0.3
• Add comment indicating digest needs to be added

.tekton/cli-main-pull-request.yaml


2. .tekton/cli-main-push.yaml ✨ Enhancement +4/-1

Add STEPS_IMAGE_STEP_NAMES to push pipeline

• Add STEPS_IMAGE_STEP_NAMES parameter with !use-trusted-artifact value
• Update tkn-bundle-oci-ta task reference from version 0.2 to 0.3
• Add comment indicating digest needs to be added

.tekton/cli-main-push.yaml


Grey Divider

Qodo Logo

@qodo-code-review
Copy link
Contributor

qodo-code-review bot commented Feb 27, 2026

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider


Action required

1. Bad step-name filter 🐞 Bug ✓ Correctness
Description
STEPS_IMAGE_STEP_NAMES is set to !use-trusted-artifact, which does not correspond to the steps
that use quay.io/conforma/cli:latest, so the intended STEPS_IMAGE replacement likely won’t be
applied to the conforma CLI steps. Additionally, the leading ! is YAML tag syntax unless quoted,
so this may not be treated as the intended literal string value.
Code

.tekton/cli-main-pull-request.yaml[R304-305]

+      - name: STEPS_IMAGE_STEP_NAMES
+        value: !use-trusted-artifact
Evidence
The PipelineRun passes value: !use-trusted-artifact as the step-names filter. In the
verify-conforma task, the step named use-trusted-artifact uses a different image
(build-trusted-artifacts), while the steps that actually use quay.io/conforma/cli:latest are named
initialize-tuf, reduce, and validate; therefore the configured step-name filter does not match
the conforma CLI steps it’s meant to target.

.tekton/cli-main-pull-request.yaml[294-320]
tasks/verify-conforma-konflux-ta/0.1/verify-conforma-konflux-ta.yaml[243-286]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`STEPS_IMAGE_STEP_NAMES` is currently set to `!use-trusted-artifact`, which (a) is not one of the step names that actually use `quay.io/conforma/cli:latest` in `verify-conforma-konflux-ta`, and (b) uses a leading `!` that YAML can interpret as tag syntax unless quoted.

### Issue Context
In `tasks/verify-conforma-konflux-ta/0.1/verify-conforma-konflux-ta.yaml`, the steps using `quay.io/conforma/cli:latest` are `initialize-tuf`, `reduce`, and `validate`, while `use-trusted-artifact` uses a different image.

### Fix Focus Areas
- .tekton/cli-main-pull-request.yaml[304-305]
- .tekton/cli-main-push.yaml[306-307]
- tasks/verify-conforma-konflux-ta/0.1/verify-conforma-konflux-ta.yaml[243-286]

### Implementation notes
- Update `STEPS_IMAGE_STEP_NAMES` to the correct step name(s) (likely a list/string of `initialize-tuf`, `reduce`, `validate`) in the format required by `task-tkn-bundle-oci-ta`.
- Ensure the YAML value is a normal string scalar (quote if needed).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


2. Unpinned task bundle 🐞 Bug ⛨ Security
Description
The tkn-bundle-oci-ta bundle reference was changed to a mutable tag (:0.3) without a digest,
making CI non-reproducible and potentially pulling different task contents over time. This also
breaks the existing pattern in these PipelineRuns where bundle-resolved tasks are digest-pinned.
Code

.tekton/cli-main-pull-request.yaml[R319-320]

+          # need to add digest
+          value: quay.io/konflux-ci/tekton-catalog/task-tkn-bundle-oci-ta:0.3
Evidence
The updated PipelineRun references task-tkn-bundle-oci-ta:0.3 without @sha256:..., while other
bundle references in the same PipelineRun are pinned by digest. This inconsistency indicates the new
reference is an outlier and introduces mutability into an otherwise digest-pinned setup.

.tekton/cli-main-pull-request.yaml[294-323]
.tekton/cli-main-pull-request.yaml[134-168]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`tkn-bundle-oci-ta` is referenced as `...:0.3` without an `@sha256:` digest, making the resolved task mutable and CI runs non-reproducible.

### Issue Context
These PipelineRuns already pin other bundle-resolved tasks by digest; `tkn-bundle-oci-ta` should follow the same pattern.

### Fix Focus Areas
- .tekton/cli-main-pull-request.yaml[318-320]
- .tekton/cli-main-push.yaml[320-322]

### Implementation notes
- Resolve the digest for `quay.io/konflux-ci/tekton-catalog/task-tkn-bundle-oci-ta:0.3` and update the `bundle:` value to include `@sha256:<digest>`.
- Remove the temporary comment once the digest is added.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

ⓘ The new review experience is currently in Beta. Learn more

Grey Divider

Qodo Logo

Comment on lines +304 to +305
- name: STEPS_IMAGE_STEP_NAMES
value: !use-trusted-artifact
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Bad step-name filter 🐞 Bug ✓ Correctness

STEPS_IMAGE_STEP_NAMES is set to !use-trusted-artifact, which does not correspond to the steps
that use quay.io/conforma/cli:latest, so the intended STEPS_IMAGE replacement likely won’t be
applied to the conforma CLI steps. Additionally, the leading ! is YAML tag syntax unless quoted,
so this may not be treated as the intended literal string value.
Agent Prompt
### Issue description
`STEPS_IMAGE_STEP_NAMES` is currently set to `!use-trusted-artifact`, which (a) is not one of the step names that actually use `quay.io/conforma/cli:latest` in `verify-conforma-konflux-ta`, and (b) uses a leading `!` that YAML can interpret as tag syntax unless quoted.

### Issue Context
In `tasks/verify-conforma-konflux-ta/0.1/verify-conforma-konflux-ta.yaml`, the steps using `quay.io/conforma/cli:latest` are `initialize-tuf`, `reduce`, and `validate`, while `use-trusted-artifact` uses a different image.

### Fix Focus Areas
- .tekton/cli-main-pull-request.yaml[304-305]
- .tekton/cli-main-push.yaml[306-307]
- tasks/verify-conforma-konflux-ta/0.1/verify-conforma-konflux-ta.yaml[243-286]

### Implementation notes
- Update `STEPS_IMAGE_STEP_NAMES` to the correct step name(s) (likely a list/string of `initialize-tuf`, `reduce`, `validate`) in the format required by `task-tkn-bundle-oci-ta`.
- Ensure the YAML value is a normal string scalar (quote if needed).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Comment on lines +319 to +320
# need to add digest
value: quay.io/konflux-ci/tekton-catalog/task-tkn-bundle-oci-ta:0.3
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

2. Unpinned task bundle 🐞 Bug ⛨ Security

The tkn-bundle-oci-ta bundle reference was changed to a mutable tag (:0.3) without a digest,
making CI non-reproducible and potentially pulling different task contents over time. This also
breaks the existing pattern in these PipelineRuns where bundle-resolved tasks are digest-pinned.
Agent Prompt
### Issue description
`tkn-bundle-oci-ta` is referenced as `...:0.3` without an `@sha256:` digest, making the resolved task mutable and CI runs non-reproducible.

### Issue Context
These PipelineRuns already pin other bundle-resolved tasks by digest; `tkn-bundle-oci-ta` should follow the same pattern.

### Fix Focus Areas
- .tekton/cli-main-pull-request.yaml[318-320]
- .tekton/cli-main-push.yaml[320-322]

### Implementation notes
- Resolve the digest for `quay.io/konflux-ci/tekton-catalog/task-tkn-bundle-oci-ta:0.3` and update the `bundle:` value to include `@sha256:<digest>`.
- Remove the temporary comment once the digest is added.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

@codecov
Copy link

codecov bot commented Feb 27, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag Coverage Δ
acceptance 55.58% <ø> (ø)
generative 18.49% <ø> (ø)
integration 27.50% <ø> (ø)
unit 68.44% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant