From 4d244b0e041f97f0e63545b67896aabce2e61f13 Mon Sep 17 00:00:00 2001
From: Paul Cantea <pcantea@whitepages.com>
Date: Fri, 6 Dec 2019 09:27:55 -0800
Subject: [PATCH] Fix reference to argo-cd server TLS data

---
 charts/argo-cd/values.yaml | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/charts/argo-cd/values.yaml b/charts/argo-cd/values.yaml
index b4d65554..7b104f77 100644
--- a/charts/argo-cd/values.yaml
+++ b/charts/argo-cd/values.yaml
@@ -633,17 +633,17 @@ configs:
     bitbucketUUÌD: ""
     gogsSecret: ""
 
-# Argo TLS Data.
-  argocdServerTlsConfig: {}
-    # key:
-    # crt: |
-    #   -----BEGIN CERTIFICATE-----
-    #   <cert data>
-    #   -----END CERTIFICATE-----
-    #   -----BEGIN CERTIFICATE-----
-    #   <ca cert data>
-    #   -----END CERTIFICATE-----
+  # Argo TLS Data.
+    argocdServerTlsConfig: {}
+      # key:
+      # crt: |
+      #   -----BEGIN CERTIFICATE-----
+      #   <cert data>
+      #   -----END CERTIFICATE-----
+      #   -----BEGIN CERTIFICATE-----
+      #   <ca cert data>
+      #   -----END CERTIFICATE-----
 
-  # Argo expects the password in the secret to be bcrypt hashed. You can create this hash with
-  # `htpasswd -nbBC 10 "" $ARGO_PWD | tr -d ':\n' | sed 's/$2y/$2a/'`
-  # argocdServerAdminPassword:
+    # Argo expects the password in the secret to be bcrypt hashed. You can create this hash with
+    # `htpasswd -nbBC 10 "" $ARGO_PWD | tr -d ':\n' | sed 's/$2y/$2a/'`
+    # argocdServerAdminPassword: