anekkanti/Rotate Temporal Cloud Service Account ApiKey
Github action that rotates the temporal cloud service account apikey and updates github secret
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Jan 8, 2025
- License
- MIT
Pinned Snippet
uses: anekkanti/github-action-rotate-temporalcloud-apikey@7fd82d9a1548bae3b9e5f0260b3a4a2192a95402 # v0.1.0tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| apikey | The apikey to use to create a new apikey. Can be the same as the one to rotate. | yes | — |
| serviceAccountId | The service account id to rotate the apikey for. | yes | — |
| apikeyNamePrefix | The prefix to use for the new apikey name. The new apikey name will be <apikeyNamePrefix>-<timestamp> | yes | — |
| duration | The number of days for which the new apikey should be valid. Default is 30 days. | — | 30 |
| description | The description to use for the new apikey. Default is 'Rotated by Github Action'. | — | Created by Github Action anekkanti/github-action-rotate-temporalcloud-apikey |
| deleteOldApikeys | Whether to delete the old apikey after creating the new one. The old apikeys will be identified by the prefix. Default is false. | — | false |
| personalAccessToken | Github token that can update secrets in the repos. | yes | — |
| repositories | List of repositories, separated by comma, to install secrets in. | yes | — |
| secretName | Name of the GH secret to update. | yes | — |
Outputs
no outputs