From 77a2a36fabeeaf09d5129c38e83a852d76cbf23c Mon Sep 17 00:00:00 2001
From: Alejandro Moreno <47833905+alemorcuq@users.noreply.github.com>
Date: Fri, 27 Sep 2019 09:27:29 +0200
Subject: [PATCH] Add missing syntax highlighting to blocks

---
 bitnami/grafana/README.md | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/bitnami/grafana/README.md b/bitnami/grafana/README.md
index 097f5824fe..738e1b2b57 100644
--- a/bitnami/grafana/README.md
+++ b/bitnami/grafana/README.md
@@ -133,7 +133,7 @@ $ helm install --name my-release -f values.yaml bitnami/grafana
 
 Grafana support multiples configuration files. Using kubernetes you can mount a file using a ConfigMap. For example, to mount a custom `grafana.ini` file or `custom.ini` file you can create a ConfigMap like the following:
 
-```
+```yaml
 apiVersion: v1
 kind: ConfigMap
 metadata:
@@ -145,7 +145,7 @@ data:
 
 And now you need to pass the ConfigMap name, to the corresponding parameter:
 
-```
+```console
 $ helm install bitnami/grafana --set config.useGrafanaIniFile=true,config.grafanaIniConfigMap=myconfig
 ```
 
@@ -156,7 +156,7 @@ A default provider is created if enabled, or you can mount your own provider usi
 Note the difference between the datasources and the dashboards creation. For the datasources we can use just one secret with all of the files, while for the dashboards we need one ConfigMap per file.
 For example, after the creation of the dashboard and datasource ConfigMap in the same way that the explained for the `grafana.ini` file, execute the following to deploy Grafana with custom dashboards:
 
-```
+```console
 $ helm install bitnami/grafana --set "dashboardsProvider.enabled=true,datasources.secretName=datasource-secret,dashboardsConfigMaps[0].configMapName=mydashboard,dashboardsConfigMaps[0].fileName=mydashboard.json"
 ```
 
@@ -169,6 +169,7 @@ $ helm install --name my-release -f ./values-production.yaml bitnami/grafana
 ```
 
 - Enable ingress controller
+
 ```diff
 - ingress.enabled: false
 + ingress.enabled: true
@@ -180,7 +181,7 @@ To enable LDAP authentication it is necessary to provide a ConfigMap with the Gr
 
 **configmap.yaml**:
 
-```
+```yaml
 apiVersion: v1
 kind: ConfigMap
 metadata:
@@ -232,13 +233,13 @@ data:
 
 Create the ConfigMap into the cluster:
 
-```bash
+```console
 $ kubectl create -f configmap.yaml
 ```
 
 And deploy the Grafana Helm Chart using the existing ConfigMap:
 
-```bash
+```console
 $ helm install bitnami/grafana --set ldap.enabled=true,ldap.configMapName=ldap-config,ldap.allowSignUp=true
 ```