feat: add bpdmStartReady toggle (#403)

Refs: eclipse-tractusx/portal-backend#845
Reviewed-By: Evelyn Gurschler <[email protected]>

charts/portal/templates/cronjob-backend-processes.yaml

@@ -141,6 +141,8 @@ spec:
               value: "{{ .Values.backend.placeholder }}"
             - name: "APPLICATIONCHECKLIST__BPDM__USEDIMWALLET"
               value: "{{ .Values.backend.useDimWallet }}"
+            - name: "APPLICATIONCHECKLIST__BPDM__STARTSHARINGSTATEASREADY"
+              value: "{{ .Values.backend.processesworker.bpdm.startSharingStateAsReady }}"
             - name: "APPLICATIONCHECKLIST__CLEARINGHOUSE__BASEADDRESS"
               value: "{{ .Values.clearinghouseAddress }}"
             - name: "APPLICATIONCHECKLIST__CLEARINGHOUSE__CLIENTID"

charts/portal/templates/deployment-backend-administration.yaml

@@ -113,6 +113,10 @@ spec:
           value: "{{ .Values.backend.processesworker.bpdm.scope }}"
         - name: "APPLICATIONCHECKLIST__BPDM__USERNAME"
           value: "{{ .Values.backend.placeholder }}"
+        - name: "APPLICATIONCHECKLIST__BPDM__USEDIMWALLET"
+          value: "{{ .Values.backend.useDimWallet }}"
+        - name: "APPLICATIONCHECKLIST__BPDM__STARTSHARINGSTATEASREADY"
+          value: "{{ .Values.backend.processesworker.bpdm.startSharingStateAsReady }}"
         - name: "APPLICATIONCHECKLIST__CLEARINGHOUSE__BASEADDRESS"
           value: "{{ .Values.clearinghouseAddress }}"
         - name: "APPLICATIONCHECKLIST__CLEARINGHOUSE__CLIENTID"

charts/portal/values.yaml

@@ -811,6 +811,10 @@ backend:
       clientId: "bpdm-client-id"
       # -- Client-secret for bpdm client-id. Secret-key 'bpdm-client-secret'.
       clientSecret: ""
+      # -- When set to true the call to set sharing state ready is skipped. This means that BPDM needs to set the state manually.
+      # When set to false, the process worker will trigger the set sharing state ready of BPDM, which means no manual interference on BPDM site is needed.
+      # This value should be aligned with the value set in the BPDM helm chart creation -> '.fromSharingMember.starts-as-ready'; if the values are not aligned the BPDM application checklist will fail.
+      startSharingStateAsReady: true
     custodian:
       membershipErrorMessage: "Credential of type MembershipCredential is already exists"
       scope: "openid"

environments/helm-values/values-int.yaml

@@ -236,6 +236,7 @@ backend:
     bpdm:
       clientId: "<path:portal/data/portal-iam-clientIds#bpdm-client-id>"
       clientSecret: "<path:portal/data/int/iam/centralidp-client-secrets#portal-bpdm-sa>"
+      startSharingStateAsReady: false
     clearinghouse:
       clientId: "<path:portal/data/int/clearinghouse#client-id>"
       clientSecret: "<path:portal/data/int/clearinghouse#client-secret>"