[SECURESIGN-3258] add ctlog-monitor

[fghanmi]

PR Type

Enhancement

---

Description

• Add ctlog-monitor image support to test constants

• Register ctlog-monitor-rhel9 repository in test data

• Update mandatory and Ansible TAS image key lists

---

Diagram Walkthrough

flowchart LR
  A["Test Constants"] -->|Add ctlog-monitor-image| B["Mandatory TAS Images"]
  A -->|Add tas_single_node_ctog_monitor_image| C["Ansible TAS Images"]
  D["Repository Data"] -->|Add ctlog-monitor-rhel9| E["Test Repositories"]

Loading

File Walkthrough

Relevant files

Enhancement

test_constants.go Add ctlog-monitor image keys to test constants                      test/support/test_constants.go Added ctlog-monitor-image to mandatory TAS operator image keys list Added tas_single_node_ctog_monitor_image to Ansible TAS image keys list Updates test constants to include new ctlog-monitor component +2/-0      repositories.json Register ctlog-monitor-rhel9 repository in test data          testdata/repositories.json Added new repository entry for rhtas/ctlog-monitor-rhel9 Set repository ID to 696ff34dec75adad72d28ac1 Marked repository as unpublished (published: false) +5/-0

---

[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: 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
🔴	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Typo in constant: The newly added key tas_single_node_ctog_monitor_image appears to contain a typo (ctog vs ctlog), making the identifier misleading and less self-documenting. Referred Code "tas_single_node_ctog_monitor_image", "tas_single_node_rekor_redis_image", Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

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

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Correct typo in image key Correct the typo in the tas_single_node_ctog_monitor_image constant to tas_single_node_ctlog_monitor_image. test/support/test_constants.go [95] -"tas_single_node_ctog_monitor_image", +"tas_single_node_ctlog_monitor_image", Apply / Chat Suggestion importance[1-10]: 8 __ Why: The suggestion correctly identifies a typo (ctog instead of ctlog) in a new constant, which would cause test failures if not fixed.	Medium
No more code suggestions