Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

[stable/sonarqube] Add MySQL database support to Sonarqube #5803

Merged
merged 5 commits into from May 31, 2018
Merged

[stable/sonarqube] Add MySQL database support to Sonarqube #5803

merged 5 commits into from May 31, 2018

Conversation

irajdeep
Copy link
Contributor

@irajdeep irajdeep commented May 29, 2018

What this PR does / why we need it:
This PR adds MySQL database support to Sonarqube. Currently Sonarqube has onlyPostgresql support to store the data. It has the relevant changes to the template files and README.md for the new MySQL database support

Which issue this PR fixes *
fixes #5654

Special notes for your reviewer:
/assign @rjkernick

…ow has an option to store data in MySQL database too, It already had a support to store the data in Postgres. A given release could now have either Postgres database (internal / external) or MySQL database (internal / external).
Updated README.md to add configuration changes that come with MySQL database support.
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels May 29, 2018
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels May 29, 2018
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels May 29, 2018
@@ -1,6 +1,6 @@
name: sonarqube
description: Sonarqube is an open sourced code quality scanning tool
version: 0.6.0
version: 0.6.1
Copy link
Collaborator

Choose a reason for hiding this comment

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

Please bump the minor version since this adds a new feature

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

heritage: {{ .Release.Service }}
type: Opaque
data:
postgres-password: {{ .Values.mysql.mysqlPassword | b64enc | quote }}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Key should be mysql-password

Copy link
Contributor Author

@irajdeep irajdeep May 29, 2018

Choose a reason for hiding this comment

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

Ah my bad , this is a blunder .

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

@@ -12,3 +12,18 @@ type: Opaque
data:
postgres-password: {{ .Values.postgresql.postgresPassword | b64enc | quote }}
{{- end -}}
{{- if eq .Values.mysql.enabled false -}}
Copy link
Collaborator

Choose a reason for hiding this comment

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

We also only need this if the database type is mysql. Same with the postgres secret above only is needed is database is postgres and postgres is disabled.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added the check , thanks for pointing out

1. Bumped the minor version of the chart since it's a feature release
2. Added check for database type while populating secrets
3. Corrected mysql key
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels May 29, 2018
@rjkernick
Copy link
Collaborator

/ok-to-test

@k8s-ci-robot k8s-ci-robot removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label May 29, 2018
@rjkernick
Copy link
Collaborator

I am going to try and test out the different combinations this afternoon before I merge it. Thanks for the quick turnaround on the changes!

@irajdeep
Copy link
Contributor Author

Sure, let me know if you find any issues . Thanks !!

@rjkernick
Copy link
Collaborator

/assign

@irajdeep
Copy link
Contributor Author

@rjkernick Can we go ahead with merging .

@rjkernick
Copy link
Collaborator

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm Indicates that a PR is ready to be merged. label May 31, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: irajdeep, rjkernick

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 31, 2018
@k8s-ci-robot k8s-ci-robot merged commit 27a7fab into helm:master May 31, 2018
or1can pushed a commit to or1can/charts that referenced this pull request Jul 10, 2018
* Added MySQL database support to Sonarqube, the Sonarqube helm chart now has an option to store data in MySQL database too, It already had a support to store the data in Postgres. A given release could now have either Postgres database (internal / external) or MySQL database (internal / external).

* Updated README.md 

Updated README.md to add configuration changes that come with MySQL database support.

* Removing white spaces to get rid of helm lint errors

* Yes another attempt to remove trailing spaces :(

* Fixing PR comments
1. Bumped the minor version of the chart since it's a feature release
2. Added check for database type while populating secrets
3. Corrected mysql key
voron pushed a commit to dysnix/helm-charts that referenced this pull request Sep 5, 2018
* Added MySQL database support to Sonarqube, the Sonarqube helm chart now has an option to store data in MySQL database too, It already had a support to store the data in Postgres. A given release could now have either Postgres database (internal / external) or MySQL database (internal / external).

* Updated README.md 

Updated README.md to add configuration changes that come with MySQL database support.

* Removing white spaces to get rid of helm lint errors

* Yes another attempt to remove trailing spaces :(

* Fixing PR comments
1. Bumped the minor version of the chart since it's a feature release
2. Added check for database type while populating secrets
3. Corrected mysql key

Signed-off-by: voron <av@arilot.com>
@runzexia
Copy link

In the sonarqube 7.1 version, mysql support was Deprecated. Do we need to roll back these changes?
https://docs.sonarqube.org/display/SONARqube71/Release+7.1+Upgrade+Notes

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Changes to Sonarqube helm chart to add MySQL support instead of Postgres.
4 participants