fix: update revision for MCO/PCO to use main candidate revision and r…

[knrc]

User description

…emove trailing spaces

---

PR Type

Bug fix

---

Description

• Add revision parameter to MCO/PCO release plan configurations

• Set revision to RHTAS-build-bot_candidate-images-main for consistency

• Remove trailing whitespace from component YAML files

---

Diagram Walkthrough

flowchart LR
  A["Release Plan Configs"] -->|Add revision param| B["RHTAS-build-bot_candidate-images-main"]
  C["Component YAML Files"] -->|Remove trailing spaces| D["Clean formatting"]

Loading

File Walkthrough

	Relevant files
Configuration changes	releaseplan.yaml Add revision parameter to release plan                                      konflux-configs/base/application/model-transparency/base/patch/releaseplan.yaml Add revision parameter with value RHTAS-build-bot_candidate-images-main Ensures model-transparency uses correct candidate image revision +2/-0      releaseplan.yaml Add revision parameter to release plan                                      konflux-configs/base/application/model-validation-operator/base/patch/releaseplan.yaml Add revision parameter with value RHTAS-build-bot_candidate-images-main Ensures model-validation-operator uses correct candidate image revision +2/-0      releaseplan.yaml Add revision parameter to release plan                                      konflux-configs/base/application/policy-controller-operator/base/patch/releaseplan.yaml Add revision parameter with value RHTAS-build-bot_candidate-images-main Ensures policy-controller-operator uses correct candidate image revision +2/-0      releaseplan.yaml Add revision parameter to release plan                                      konflux-configs/base/application/policy-controller/base/patch/releaseplan.yaml Add revision parameter with value RHTAS-build-bot_candidate-images-main Ensures policy-controller uses correct candidate image revision +2/-0
Formatting	component.yaml Remove trailing whitespace                                                              konflux-configs/base/application/model-validation-operator/base/component.yaml Remove trailing whitespace from componentName field Improves code formatting consistency +1/-1      component.yaml Remove trailing whitespace                                                              konflux-configs/base/application/policy-controller-operator/base/component.yaml Remove trailing whitespace from componentName field Improves code formatting consistency +1/-1

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.

[tommyd450]

Deployed on testing cluster within rhtas-dev-tenant namespace, looks fine to me. LGTM