akeyless-community/Akeyless Authentication and fetching secrets
Akeyless Authentication and fetching secrets
View on GitHubTrust Signals
- Scorecard Score
- Scorecard 4–6scored Jul 13, 2026
- Maintenance Recency
- Activelast commit Jun 3, 2026
- License
- MPL 2.0
Pinned Snippet
uses: akeyless-community/akeyless-github-action@618b75a405b4755a56a7766c80f8c3dc617070e7 # v1.1.6tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| access-id | Akeyless Access ID, Unless token is provided, it is required. | no | — |
| access-type | The method to use to authenticate with Akeyless Vault, Unless token is provided, it is required. | no | jwt |
| token | Akeyless authentication token. | no | — |
| api-url | The API endpoint to use, defaults to https://api.akeyless.io. | no | https://api.akeyless.io |
| access-key | Akeyless Access Key | no | — |
| gcp-audience | GCP audience to use in signed JWT (relevant only for access-type=gcp) | no | akeyless.io |
| gateway-url | Gateway URL for the K8S authenticated (relevant only for access-type=k8s) | no | — |
| k8s-auth-config-name | The K8S Auth config name (relevant only for access-type=k8s) | no | — |
| ca-certificate | The CA certificate for the authentication to gateway | no | — |
| static-secrets | A YAML list representing static secrets to fetch | no | — |
| dynamic-secrets | A YAML list representing dynamic secrets to fetch. | no | — |
| rotated-secrets | A YAML list representing rotated secrets to fetch. | no | — |
| ssh-certificates | A YAML list representing ssh certificates to fetch. | no | — |
| pki-certificates | A YAML list representing pki certificates to fetch. | no | — |
| export-secrets-to-outputs | True/False to denote if static/dynamic secrets should be exported as action outputs. | no | true |
| export-secrets-to-environment | True/False to denote if static/dynamic secrets should be exported as environment variables. | no | true |
| parse-json-secrets | True/False to denote if environment variables should be created for each key/value pair in the JSON of the secret. | no | false |
| create-secret-name | Name of the new secret to create | no | — |
| create-secret-value | Value of the new secret to create | no | — |
| update-secret-name | Name of the existing secret to update | no | — |
| update-secret-value | New value to update the secret with | no | — |
Outputs
| name | description |
|---|---|
| token | Akeyless Token |