xiaxinhang/pr-agent
1
0
Fork 0
mirror of https://github.com/qodo-ai/pr-agent.git synced 2025-07-03 20:30:41 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: detailed description

Browse Source
This commit is contained in:
tomoya-kawaguchi
2025-05-29 13:44:33 +09:00
parent 32b1fb91c3
commit d1e8d267f6
1 changed files with 14 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -207,16 +207,23 @@ For example: `GITHUB.WEBHOOK_SECRET` --> `GITHUB__WEBHOOK_SECRET`
For production Lambda deployments, use AWS Secrets Manager instead of environment variables: For production Lambda deployments, use AWS Secrets Manager instead of environment variables:
1. Create a secret in AWS Secrets Manager with your configuration 1. Create a secret in AWS Secrets Manager with JSON format like this:
2. Add IAM permissions for `secretsmanager:GetSecretValue`
3. Set the secret ARN in your Lambda environment:
```bash ```json
AWS_SECRETS_MANAGER__SECRET_ARN=arn:aws:secretsmanager:region:account:secret:name {
CONFIG__SECRET_PROVIDER=aws_secrets_manager "openai.key": "sk-proj-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"github.webhook_secret": "your-webhook-secret-from-step-2",
"github.private_key": "-----BEGIN RSA PRIVATE KEY-----\nMIIEpAIBAAKCAQEA...\n-----END RSA PRIVATE KEY-----"
}
``` ```
For detailed setup instructions, see [AWS Secrets Manager Integration](../usage-guide/aws_secrets_manager.md). 2. Add IAM permission `secretsmanager:GetSecretValue` to your Lambda execution role
3. Set these environment variables in your Lambda:
```bash
AWS_SECRETS_MANAGER__SECRET_ARN=arn:aws:secretsmanager:us-east-1:123456789012:secret:pr-agent-secrets-AbCdEf
CONFIG__SECRET_PROVIDER=aws_secrets_manager
```
--- ---