fix: add build-nudges-ref for console components

[osmman]

Why

rhtas-console (API) and rhtas-console-ui components are missing build-nudges-ref to rhtas-operator and artifact-signer-ansible. When a new console image is built in Konflux, the operator's images.env is never updated automatically — digests must be set manually, which led to a broken (non-existent) digest being deployed.

What

• Add build-nudges-ref to both rhtas-console and rhtas-console-ui Component definitions, targeting artifact-signer-ansible and rhtas-operator (matching the pattern used by all other operator-consumed components)
• The fix is in the shared template base, so it applies to all streams (main, v1-4, etc.)

[qodo-for-securesign]

PR Summary by Qodo

Fix Konflux build nudges for console components

🐞 Bug fix ⚙️ Configuration changes 🕐 Less than 10 minutes

AI Description

• Add Konflux build nudges from console images to operator and ansible components.
• Ensure console rebuilds automatically propagate digest updates into operator-managed deployments.
• Apply the fix in the shared base template to cover all release streams.

Diagram

graph TD
  A[Konflux build: rhtas-console] --> B["build-nudges-ref"] --> C[rhtas-operator]
  A --> B --> D[artifact-signer-ansible]
  E[Konflux build: rhtas-console-ui] --> B --> C
  E --> B --> D
  F["rhtas-console.yaml (base overlay)"] --> A
  F --> E

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Add nudges only in per-stream overlays

• ➕ Allows stream-specific downstream targets if they ever diverge
• ➖ Higher maintenance and easy to miss new streams
• ➖ Does not match the stated goal of a single shared fix across all streams

2. Downstream polling/sync job for image digest updates

• ➕ Decouples digest propagation from Konflux component metadata
• ➕ Can provide additional validation/guardrails before updating deployments
• ➖ More moving parts and operational burden
• ➖ Still doesn’t align with the existing 'build nudges' pattern used elsewhere in this repo

Recommendation: The chosen approach (adding build-nudges-ref in the shared base template) is the best fit: it matches the established operator-consumed component pattern, fixes the missed automation point directly at the source, and applies consistently across all streams without duplicating configuration.

Files changed (1) +6 / -0

Bug fix (1) +6 / -0

rhtas-console.yamlAdd build-nudges-ref for console API and UI components +6/-0

Add build-nudges-ref for console API and UI components

• Adds build-nudges-ref entries to both rhtas-console and rhtas-console-ui component specs. This ensures console image rebuilds automatically nudge artifact-signer-ansible and rhtas-operator so downstream digest updates are propagated instead of requiring manual intervention.

konflux-configs/base/project/overlay/rhtas-console/patch/rhtas-console.yaml

[github-actions]

Configuration Diff

2 document(s) impacted:

+ 0 added
- 0 removed
! 2 modified

Diff

@@ spec.resources.appstudio.redhat.com/v1alpha1/Component/rhtas-console{{.nameSuffix}}.spec @@
# projctl.konflux.dev/v1beta1/ProjectDevelopmentStreamTemplate/rhtas-tenant/rhtas-console-template
! + one map entry added:
+   build-nudges-ref:
+   - artifact-signer-ansible{{.nameSuffix}}
+   - rhtas-operator{{.nameSuffix}}

@@ spec.resources.appstudio.redhat.com/v1alpha1/Component/rhtas-console-ui{{.nameSuffix}}.spec @@
# projctl.konflux.dev/v1beta1/ProjectDevelopmentStreamTemplate/rhtas-tenant/rhtas-console-template
! + one map entry added:
+   build-nudges-ref:
+   - artifact-signer-ansible{{.nameSuffix}}
+   - rhtas-operator{{.nameSuffix}}

---

_{📦 Artifacts: base-output.yaml, head-output.yaml, dyff-output.txt}

[qodo-for-securesign]

Code Review by Qodo

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

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}