supabase-kubernetes
supabase-kubernetes copied to clipboard
Bug fix Supabase storage: use right secret key when providing S3 access keys via secrets
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
When providing the S3 access keys via secrets, the keyId is used for both AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env variables.
What is the new behavior?
When providing the S3 access keys via secrets, the accessKey is used for the AWS_SECRET_ACCESS_KEY env variable.
Additional context
None