chore: use GitHub secrets instead of hashicorp vault for now

tokens-studio · Jul 4, 2024 · d4f35b2 · d4f35b2
1 parent fb57cdf
commit d4f35b2
Showing 1 changed file with 13 additions and 11 deletions.
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
@@ -36,16 +36,17 @@ jobs:
       - name: Install Dependencies
         run: npm ci
 
-      - name: Import Secrets
-        id: secrets
-        uses: hashicorp/vault-action@v2
-        with:
-          url: ${{ vars.VAULT_URL }}
-          role: ${{ vars.VAULT_ROLE }}
-          method: jwt
-          namespace: admin
-          secrets: |
-            ${{ vars.VAULT_PATH }} TOKEN | NPM_TOKEN;
+      # FIXME: not working ....
+      # - name: Import Secrets
+      #   id: secrets
+      #   uses: hashicorp/vault-action@v2
+      #   with:
+      #     url: ${{ vars.VAULT_URL }}
+      #     role: ${{ vars.VAULT_ROLE }}
+      #     method: jwt
+      #     namespace: admin
+      #     secrets: |
+      #       ${{ vars.VAULT_PATH }} TOKEN | NPM_TOKEN;
 
       - name: Create Release Pull Request or Publish to npm
         id: changesets
@@ -55,4 +56,5 @@ jobs:
           publish: npm run release
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          NODE_AUTH_TOKEN: ${{ steps.secrets.outputs.NPM_TOKEN }}
+          # NODE_AUTH_TOKEN: ${{ steps.secrets.outputs.NPM_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}