[hung-nguyen-hoang]

Jira: GRIF-1221

Summary by CodeRabbit

• Chores
  • Updated the underlying components used for Redshift connectivity. No end-user-facing features or behavior changes are included in this release.

[coderabbitai]

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: e16e0dc2-81bb-4598-b7f7-5dd8a65b7318

Commits

Reviewing files that changed from the base of the PR and between 002e4d9 and 4821d42.

Files selected for processing: 2

• VERSION
• ci/redshift/pom.xml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Walkthrough

The Redshift JDBC and AWS SDK dependencies were updated. The project version changed from 3.7.108 to 3.7.109.

Changes: Redshift dependency update

Layer / File(s)	Summary
Dependency and version update ci/redshift/pom.xml, VERSION	The JDBC dependency changed to version 2.2.9. AWS SDK v1 dependencies were replaced with AWS SDK v2 dependencies at version 2.31.2, and Jackson Databind 2.16.0 was added. The project version changed to 3.7.109.

Priority: Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Suggested labels: renovate

Suggested reviewers: phong-nguyen-duy

Merge Risk: Minimal · up to 4821d

This change upgrades the Redshift JDBC driver and bumps the version. The existing basic-authentication path continues to work with the new driver, and no merge-blocking issue remains.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: upgrading the Redshift JDBC driver to version 2.2.9.
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

Finishing Touches: 💡 1

🛠️ Fix failing CI checks: 💡

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{A rabbit checks the driver’s name,
New versions join the build’s refrain.
The SDK steps forward, too,
With Jackson added to the crew.
A version hops to one-oh-nine,
Then carrots make the tests align.}

_{Comment @coderabbitai help to get the list of available commands.}

[milandufek]

🌻

[yenkins]

LCM bricks image available

New image stable/lcm-bricks is available.

Version	3.7.109
Build tag	202610300733.5524efb1

Next steps

1. Tag the image with its major version
Run the LCM: Retag stable image to major version workflow dispatch:

• Go to Actions → LCM: Retag stable image to major version → Run workflow
• Set tag to 3.7.109
• Leave dry-run unchecked and click Run workflow

Or via gh CLI:

gh workflow run lcm-stable-retag.yaml --repo gooddata/gooddata-ruby -f tag=3.7.109 -f dry-run=false

2. Register bricks to prod clusters
Once the retag completes, manually run the respective Rundeck job for each cluster: rundeck-sslauth.na.intgdc.com