adapt sonarqube config for new sonarqube pipeline changes

Author: BraisVQ

configuration-sample/ods-core.env.sample

@@ -174,6 +174,12 @@ SONARQUBE_DB_MEMORY_LIMIT=512Mi
 SONARQUBE_DB_CAPACITY=2Gi
 SONARQUBE_DB_BACKUP_CAPACITY=1Gi
 
+# SonarQube scan configuration
+SONAR_SCAN_ENABLED=true
+SONAR_SCAN_EXCLUSIONS=
+SONAR_SCAN_NEXUS_REPOSITORY=leva-documentation
+SONAR_SCAN_ALERT_EMAILS=
+
 #########
 # Jira #
 #########

sonarqube/chart/Chart.yaml

@@ -15,7 +15,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 1.1.1
+version: 1.1.2
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

sonarqube/chart/templates/cm-scan.yaml

@@ -0,0 +1,11 @@
+kind: ConfigMap
+metadata:
+  labels:
+    app: {{ .Values.global.appName }}-scan
+  name: {{ .Values.global.appName }}-scan
+apiVersion: v1
+data:
+  alertEmails: {{ .Values.scan.sonaralertEmails }} 
+  enabled: {{ .Values.scan.sonarEnabled }} 
+  exclusions: {{ .Values.scan.sonarExclusions }} 
+  nexusRepository: {{ .Values.scan.sonarNexusRepository }} 

sonarqube/chart/templates/cm.yaml sonarqube/chart/templates/cm-server.yamlsonarqube/chart/templates/cm.yaml renamed to sonarqube/chart/templates/cm-server.yaml

@@ -46,3 +46,8 @@ buildConfig:
   cpuLimit: 1
   memRequest: 1Gi
   memLimit: 2Gi
+scan:
+  sonarEnabled: $SONAR_SCAN_ENABLED
+  sonarExclusions: $SONAR_SCAN_EXCLUSIONS
+  sonarNexusRepository: $SONAR_SCAN_NEXUS_REPOSITORY
+  sonaralertEmails: $SONAR_SCAN_ALERT_EMAILS