Description
Currently when the infisical-secrets-action fetches secrets using OIDC authentication, the short-lived access token retrieved during this process is not exposed.
It would be very useful if the action could output the OIDC access token, so that it can be consumed by subsequent steps in the workflow. This would allow us to launch some additional API call directly in the same job, leveraging the already authenticated token without re-authenticating.
Example use case
jobs:
secrets:
runs-on: ubuntu-latest
steps:
- name: Fetch Infisical Secrets
id: infisical
uses: infisical/infisical-secrets-action@vX
with:
method: oidc
- name: Use run CLI with OIDC token
run: |
script using access token to auth to infisical
Description
Currently when the
infisical-secrets-actionfetches secrets using OIDC authentication, the short-lived access token retrieved during this process is not exposed.It would be very useful if the action could output the OIDC access token, so that it can be consumed by subsequent steps in the workflow. This would allow us to launch some additional API call directly in the same job, leveraging the already authenticated token without re-authenticating.
Example use case