Move lago chart to a more standard chart structure

.github/workflows/chart-testing.yml

@@ -10,29 +10,29 @@ jobs:
         uses: actions/checkout@v4
         with:
           fetch-depth: 0
-      
+
       - name: Set up Helm
         uses: azure/setup-helm@v3
         with:
           version: v3.12.1
-      
+
       - name: Set up Python
         uses: actions/setup-python@v5
         with:
-          python-version: '3.10'
+          python-version: "3.10"
           check-latest: true
-      
+
       - name: Set up chart-testing
         uses: helm/[email protected]
 
       - name: Run chart-testing (list-changed)
         id: list-changed
         run: |
-          changed=$(ct list-changed --target-branch ${{ github.event.repository.default_branch }})
+          changed=$(ct list-changed --config ct.yaml)
           if [[ -n "$changed" ]]; then
             echo "changed=true" >> "$GITHUB_OUTPUT"
           fi
-      
+
       - name: Run chart-testing (lint)
         if: steps.list-changed.outputs.changed == 'true'
-        run: ct lint --target-branch ${{ github.event.repository.default_branch }}
+        run: ct lint --config ct.yaml

values.yaml → charts/lago/values.yaml

@@ -2,8 +2,8 @@ version: 1.17.4
 
 # Required: Set the URLs for your API and Frontend services
 # Replace these placeholders with the actual domain names.
-apiUrl: "" # Example: https://api.mydomain.dev
-frontUrl: "" # Example: https://app.mydomain.dev
+apiUrl: ""   # Example: https://api.mydomain.dev
+frontUrl: ""   # Example: https://app.mydomain.dev
 
 # Only for Development, Staging or PoC, you should use a managed Redis instance for Production
 redis:
@@ -24,12 +24,12 @@ postgresql:
 
 global:
   # Define your Lago Premium License
-  #license:
+  # license:
   # If you use a managed PG instance
   # Should respect this format postgresql://USER:PASSWORD@HOST:PORT/DATABASE_NAME
-  #databaseUrl:
+  # databaseUrl:
   # Should respect standard redis URL format redis://..., redis+sentinel://...
-  #redisUrl:
+  # redisUrl:
 
   # If you wish to provide an existing secret with credentials in, then you can do so here.
   # The following fields are required:
@@ -39,7 +39,7 @@ global:
   #  - awsS3SecretAccessKey:
   #  - smtpUsername:
   #  - smtpPassword:
-  #existingSecret: "lago-credentials"
+  # existingSecret: "lago-credentials"
   # Not required if using existingSecret
   postgresql:
     auth:
@@ -56,23 +56,23 @@ global:
   s3:
     enabled: false
     # accessKeyId and secretAccessKey are not required here if using existingSecret
-    #accessKeyId: "<your-aws-access-key>"
-    #secretAccessKey: "<your-aws-secret-key>"
-    #bucket: "<your-aws-bucket>"
-    #region: "<your-aws-region>"
-    #endpoint: "https://s3.<region>.amazonaws.com" # Leave empty for default AWS S3 endpoint
+    # accessKeyId: "<your-aws-access-key>"
+    # secretAccessKey: "<your-aws-secret-key>"
+    # bucket: "<your-aws-bucket>"
+    # region: "<your-aws-region>"
+    # endpoint: "https://s3.<region>.amazonaws.com" # Leave empty for default AWS S3 endpoint
 
   smtp:
     # username and password are not required here if using existingSecret
     enabled: false
-    #address:
-    #username:
-    #password:
-    #port:
-    #fromEmail:
+    # address:
+    # username:
+    # password:
+    # port:
+    # fromEmail:
   newRelic:
     enabled: false
-    #key:
+    # key:
 
   # You can disable Lago's signup
   signup:
@@ -90,10 +90,10 @@ global:
     egress: []
     ingress: []
 
-  #serviceAccountName:
+  # serviceAccountName:
 
   # If kubectlVersion is not supplied it will be inferred using the version of the cluster that Lago is deployed on.
-  #kubectlVersion: 1.29
+  # kubectlVersion: 1.29
 
 front:
   replicas: 1

ct.yaml

@@ -0,0 +1,8 @@
+remote: origin
+target-branch: main
+chart-dirs:
+  - charts
+chart-repos:
+  - bitnami=https://charts.bitnami.com/bitnami
+  - minio=https://charts.min.io/
+validate-maintainers: false