CI: Move secret definition under secrets

Error: composed-ci-management-verify.yaml@main (Line: 148, Col: 20): Invalid secret, ENV_SECRETS is not defined in the referenced workflow. Signed-off-by: Anil Belur <[email protected]>
lfit · Nov 21, 2023 · 217ba09 · 217ba09
1 parent b7e4634
commit 217ba09
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 4 deletions.
diff --git a/.github/workflows/compose-maven-verify.yaml b/.github/workflows/compose-maven-verify.yaml
@@ -122,7 +122,7 @@ jobs:
       - name: Export env secrets
         uses: infovista-opensource/[email protected]
         with:
-          secrets: ${{ inputs.ENV_SECRETS }}
+          secrets: ${{ secrets.ENV_SECRETS }}
       - name: Obtain global settings file
         # yamllint disable rule:line-length
         run: |

diff --git a/.github/workflows/compose-packer-verify.yaml b/.github/workflows/compose-packer-verify.yaml
@@ -47,13 +47,11 @@ on:
         required: false
         default: "{}"
         type: string
+    secrets:
       ENV_SECRETS:
         # yamllint disable-line rule:line-length
         description: "Pass GitHub secrets to be exported as environment variables via `toJSON(secrets)` or specific secrets encoded in JSON format"
         required: false
-        default: "{}"
-        type: string
-    secrets:
       CLOUDS_ENV_B64:
         description: "Packer cloud environment credentials"
         required: true