xiaxinhang/pr-agent
1
0
Fork 0
mirror of https://github.com/qodo-ai/pr-agent.git synced 2025-07-02 11:50:37 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: update document for Secrets Manager

Browse Source
This commit is contained in:
tomoya-kawaguchi
2025-05-29 13:09:58 +09:00
parent 5e535a8868
commit 53e232d7f4
2 changed files with 1 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docs/installation/github.md
View File

@ -203,7 +203,7 @@ For example: `GITHUB.WEBHOOK_SECRET` --> `GITHUB__WEBHOOK_SECRET`
7. Go back to steps 8-9 of [Method 5](#run-as-a-github-app) with the function url as your Webhook URL.
The Webhook URL would look like `https://<LAMBDA_FUNCTION_URL>/api/v1/github_webhooks`
### Using AWS Secrets Manager (Recommended)
### Using AWS Secrets Manager
For production Lambda deployments, use AWS Secrets Manager instead of environment variables:

11
docs/docs/usage-guide/additional_configurations.md
View File

@ -250,14 +250,3 @@ Where the `ignore_pr_authors` is a list of usernames that you want to ignore.
!!! note
There is one specific case where bots will receive an automatic response - when they generated a PR with a _failed test_. In that case, the [`ci_feedback`](https://qodo-merge-docs.qodo.ai/tools/ci_feedback/) tool will be invoked.
## Secret Management
For production deployments, consider using external secret management:
- **AWS Secrets Manager**: Recommended for AWS Lambda deployments
- **Google Cloud Storage**: For Google Cloud environments
External secret providers automatically override environment variables at startup, providing enhanced security for sensitive information like API keys and webhook secrets.
See [Configuration Options](configuration_options.md#secret-providers) for setup details.