fix: use proper secret for RADAS

Pass the `RADAS_CONFIG_PATH` as env secret

Signed-off-by: Jonathan Gangi <jgangi@redhat.com>

Author: JAVGan

pipelines/managed/slan-cuan-release/slan-cuan-release.yaml

@@ -99,12 +99,6 @@ spec:
       default: "false"
 
     # Sign parameters
-    - name: radas-config-secret
-      description: |
-        Kubernetes Secret name containing RADAS configuration JSON.
-        The secret must have a `config.json` key with RADAS API URL and credentials
-      type: string
-      default: "radas-config"
     - name: requester-id
       description: |
         Requester identity for signing operations.
@@ -359,6 +353,12 @@ spec:
             value: $(params.taskGitRevision)
           - name: pathInRepo
             value: tekton/tasks/slan-cuan-sign.yaml
+        env:
+          - name: RADAS_CONFIG_PATH
+            valueFrom:
+              secretKeyRef:
+                name: radas-cfg
+                key: radas_cfg.json
       runAfter:
         - extract
         - collect-task-params
@@ -367,8 +367,6 @@ spec:
           value: $(tasks.collect-snapshot-params.results.extractedValues[0])
         - name: SIGNING_KEY
           value: $(tasks.collect-task-params.results.extractedValues[2])
-        - name: RADAS_CONFIG_SECRET
-          value: $(params.radas-config-secret)
         - name: REQUESTER_ID
           value: $(params.requester-id)
         - name: ZIP_ROOT_PATH