Skip to content

fix(sonarqube): source JDBC password from sonarqube-postgresql (Vault) - #19

Merged
emmanuelbruno merged 1 commit into
mainfrom
fix/sq-jdbc-secret-source
Sep 19, 2026
Merged

emmanuelbruno merged 1 commit into
mainfrom
fix/sq-jdbc-secret-source

Conversation

@emmanuelbruno

Copy link
Copy Markdown
Contributor

SonarQube read its DB password from CNPG-generated sonarqube-db-app while the app role is sourced from Vault via sonarqube-postgresql (DatabaseRole). They diverge on Vault rotation -> SQ loses DB auth. Point SQ at sonarqube-postgresql (same source as the role). Bump valueURL cache-buster.

Copilot AI lite review requested due to automatic review settings September 18, 2026 22:20

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟢 Approval recommended

The changed Secret exists and is the same credential source referenced by the SonarQube DatabaseRole.

Review effort: Lite
Findings: None

What changed in this PR

Aligns SonarQube’s JDBC password with the Vault-backed secret used by its CNPG DatabaseRole, preventing credential drift.

Changes:

  • Uses sonarqube-postgresql for JDBC credentials.
  • Bumps the ArgoCD values URL cache-buster.
File Description
helm/​releases/​sonarqube/​values.yaml Points JDBC password sourcing to the Vault-backed Secret.
bootstrap/​appset-helm.yaml Forces ArgoCD to reload updated Helm values.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@emmanuelbruno
emmanuelbruno merged commit c4c5bb7 into main Sep 19, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants