aasmal97/Render Secrets Sync
Update secrets on a Render Service, programmatically
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Nov 5, 2024
- License
- MIT
Pinned Snippet
uses: aasmal97/rendersecretssync@fe9cef21c7236f109ebea5182fc4e7dd36e32c73 # v1.1.0tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| ENV_FILE_PATH | The file path to the .env file that we will read to update render on | yes | "" |
| RENDER_API_KEY | Render API key, which we will use to make requests to Render | yes | "" |
| RENDER_SERVICE_NAME | Render service name, that identifies the service we will target, to update secrets on. This must be unique! If you have more than one service that shares the same name, the change will occur on the first one found. | yes | "" |
| DELETE_ALL_NOT_IN_ENV | Delete all secrets not found in the .env file. | no | false |
| DELAY_DEPLOY_AFTER_SECRETS | Delay deployment by this many milliseconds after secrets have been updated. | no | 0 |
Outputs
no outputs