chore: add config maps for test seeding data

Refs: #205

charts/ssi-credential-issuer/templates/job-issuer-migrations.yaml

@@ -66,11 +66,17 @@ spec:
           - name: "SEEDING__TESTDATAENVIRONMENTS__0"
             value: "{{ .Values.migrations.seeding.testDataEnvironments }}"
           - name: "SEEDING__DATAPATHS__0"
-            value: "{{ .Values.migrations.seeding.testDataPaths }}"
+            value: "Seeder/Data"           
+          {{- if and (.Values.migrations.seeding.testData.configMap) (.Values.migrations.seeding.testData.filename) }}
+          - name: "SEEDING__DATAPATHS__1"
+             value: "Seeder/Data/import"
+          - name: "SEEDING__TESTDATAENVIRONMENTS__1"
+             value: "{{ .Values.migrations.seeding.testData.filename }}"
+          {{- end }}
           - name: "SERILOG__MINIMUMLEVEL__Default"
             value: "{{ .Values.migrations.logging.default }}"
           - name: "PROCESSIDENTITY__IDENTITYID"
-            value: "{{ .Values.migrations.processIdentity.identityId }}"
+            value: "ac1cf001-7fbc-1f2f-817f-bce058020006"
         ports:
         - name: http
           containerPort: {{ .Values.portContainer }}

charts/ssi-credential-issuer/values.yaml

@@ -86,11 +86,13 @@ migrations:
       memory: 200M
   seeding:
     testDataEnvironments: ""
-    testDataPaths: "Seeder/Data"
+    testData:
+      # -- ConfigMap containing json files for the tables to seed, e.g. companies.test.json, addresses.test.json, etc.
+      configMap: ""
+      # -- Filename identifying the test data files e.g. for companies.test.json the value would be "test"
+      filename: ""
   logging:
     default: "Information"
-  processIdentity:
-    identityId: ac1cf001-7fbc-1f2f-817f-bce058020006
 
 processesworker:
   name: "processesworker"

environments/argocd-app-templates/appsetup-int.yaml

@@ -36,3 +36,45 @@ spec:
         - name: helm_args
           value: '-f values.yaml -f ../../environments/helm-values/values-int.yaml'
   project: project-portal
+data:
+  use_cases.test.json: |-
+    [
+      {
+        "id": "1aacde78-35ec-4df3-ba1e-f988cddcbbd9",
+         "name": "None",
+         "shortname": "None"
+      }
+    ]
+  verified_credential_external_type_detail_versions.test.json: |-
+    [
+      {
+        "id": "d0f05b79-792c-4cb8-9b8d-6e476ac2e926",
+        "verified_credential_external_type_id": 2,
+        "version": "0.0",
+        "template": "https://catena-x.net/fileadmin/user_upload/04_Einfuehren_und_umsetzen/Governance_Framework/231016_Catena-X_Use_Case_Framework_PCF.pdf",
+        "valid_from": "2023-01-01 00:00:00.000000 +00:00",
+        "expiry": "2023-12-31 00:00:00.000000 +00:00"
+      },
+      {
+        "id": "2d17a933-f65f-49cd-84a9-cff299a79f85",
+        "verified_credential_external_type_id": 11,
+        "version": "1.0",
+        "template": "https://catena-x.net/fileadmin/user_upload/04_Einfuehren_und_umsetzen/Governance_Framework/example.pdf",
+        "valid_from": "2024-10-16 00:00:00.000000 +00:00",
+        "expiry": "2025-10-16 00:00:00.000000 +00:00"
+      }
+    ]
+  verified_credential_type_assigned_external_types.test.json: |-
+    [
+      {
+        "verified_credential_external_type_id": 11,
+        "verified_credential_type_id": 11
+      }
+    ]
+  verified_credential_type_assigned_use_cases.test.json: |-
+    [
+      {
+        "verified_credential_type_id": 11,
+        "use_case_id": "1aacde78-35ec-4df3-ba1e-f988cddcbbd9"
+      }
+    ]