chore: update Qodo config to v2

[zdrapela]

Description

Update to the Qodo configuration to v2: https://docs.qodo.ai/code-review/migrating-to-qodo-v2

Mirrors changes from redhat-developer/rhdh#4460.

https://redhat.atlassian.net/browse/RHIDP-12920

[rhdh-qodo-merge]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🔒 No security concerns identified

⚡ Recommended focus areas for review Config Types Several config values appear to be set as quoted strings (e.g., "true"/"false") rather than TOML booleans. Confirm whether Qodo v2 expects actual booleans here; if so, use true/false without quotes to avoid the agent ignoring or misinterpreting these settings. [checks] enable_auto_checks_feedback = "true" persistent_comment = "true" final_update_message = "false" Supply Chain The workflow updates tombi to a new version and checksum. Validate that the pinned tool version matches the provided checksum and that the action version/comment aligns with the intended release, to prevent CI breakages or integrity-check failures. - uses: tombi-toml/setup-tombi@cebfd308ba02edadfcee148b7473536990950c92 # v1.0.8 with: version: 'v0.9.9' checksum: 'b50dbc90ec27591dbaf564b628bd3b3e4ead371a60931bc8ea5f34d7cd1d3607'

📄 References redhat-developer/rhdh-operator/dist/rhdh/install.yaml [1816-1824] redhat-developer/rhdh-operator/dist/rhdh/install.yaml [1794-1816] redhat-developer/rhdh/scripts/rhdh-openshift-setup/values.yaml [271-310] redhat-developer/rhdh/scripts/rhdh-openshift-setup/values.yaml [324-336] redhat-developer/rhdh-operator/dist/rhdh/install.yaml [2895-2927] redhat-developer/rhdh-operator/dist/rhdh/install.yaml [431-438] redhat-developer/rhdh-operator/dist/rhdh/install.yaml [2263-2279] redhat-developer/rhdh-operator/dist/rhdh/install.yaml [1824-1826]

[rhdh-qodo-merge]

PR Type

Enhancement, Configuration changes

---

Description

• Update Qodo configuration from v1 to v2 with new command structure

• Migrate JIRA URL to Atlassian cloud and remove API token reference

• Replace legacy review/describe commands with agentic equivalents

• Reorganize configuration sections and update TOML validator version

---

File Walkthrough

	Relevant files
Dependencies	toml-checks.yaml Update TOML validator to v0.9.9                                                    .github/workflows/toml-checks.yaml Update tombi-toml action version tag from v1 to v1.0.8 Bump TOML validator version from v0.6.3 to v0.9.9 Update checksum for new validator version +3/-3
Configuration changes	.pr_agent.toml Migrate to Qodo v2 configuration format                                    .pr_agent.toml Replace /review and /describe commands with /agentic_review and /agentic_describe Add new /generate_labels command to pr_commands Migrate JIRA URL from issues.redhat.com to redhat.atlassian.net Remove jira_api_token and feedback_on_draft_pr settings Restructure configuration sections: consolidate review settings into [review_agent], create new [pr_test] and [checks] sections Simplify configuration by removing enable_pr_diagram, commitable_code_suggestions, and other deprecated options +12/-22

---

[rhdh-qodo-merge]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
High-level	The PR may unintentionally disable existing review checks The suggestion questions if the removal of require_ticket_analysis_review = true during the v2 configuration migration is intentional, as the new configuration does not explicitly preserve this quality gate. It recommends clarifying this potential impact. Examples: .pr_agent.toml [15-21] [review_agent] comments_location_policy = "summary" [checks] enable_auto_checks_feedback = "true" persistent_comment = "true" final_update_message = "false" Solution Walkthrough: Before: # .pr_agent.toml [pr_reviewer] # /review # persistent_comment = true require_tests_review = false require_ticket_analysis_review = true enable_review_labels_security = true enable_review_labels_effort = true After: # .pr_agent.toml # The [pr_reviewer] section is removed. [review_agent] comments_location_policy = "summary" [checks] enable_auto_checks_feedback = "true" persistent_comment = "true" final_update_message = "false" # It is unclear if the functionality of 'require_ticket_analysis_review' is preserved. Suggestion importance[1-10]: 8 __ Why: The suggestion correctly identifies the removal of the require_ticket_analysis_review setting, raising a valid and significant concern about a potential loss of a critical quality gate in the PR review process.	Medium
Possible issue	✅ Use boolean types Suggestion Impact: Updated the TOML config to use boolean literals for enable_auto_checks_feedback, persistent_comment, and final_update_message instead of quoted strings. code diff: -enable_auto_checks_feedback = "true" -persistent_comment = "true" -final_update_message = "false" +enable_auto_checks_feedback = true +persistent_comment = true +final_update_message = false Replace string values like "true" and "false" with boolean literals true and false in the TOML configuration for correct parsing. .pr_agent.toml [19-21] -enable_auto_checks_feedback = "true" -persistent_comment = "true" -final_update_message = "false" +enable_auto_checks_feedback = true +persistent_comment = true +final_update_message = false [Suggestion processed] Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies that string literals are used for boolean values in the TOML configuration, which could lead to misinterpretation and incorrect behavior.	Medium
Update

[rm3l]

/override "docker compose - developer-lightspeed-safety-guard"

Unrelated

[openshift-ci]

@rm3l: Overrode contexts on behalf of rm3l: docker compose - developer-lightspeed-safety-guard

Details

In response to this:

/override "docker compose - developer-lightspeed-safety-guard"

Unrelated

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.