hasura / hasura/graphql-engine

Can't use auto-generated PG password with special characters

Open
#9,897 0 comments 0 reactions 0 assignees View on GitHub
k/bug
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Version Information

Server Version: v2.32.1
CLI Version (for CLI related issue): v2.32.1

### Environment
OSS

### What is the current behaviour?
I'm switching my self-hosted setup on AWS ECS to use database credentials that are auto-rotated automatically through AWS Secrets Manager. I don't have control over the contents of the secret as it's controlled by RDS.

As the secret only provides the username and password, I split up the connection string into multiple env vars and interpolated them together in the metadata.

When trying to connect, I get this error from PG, which to my understanding is due to special characters in the password field.

Is there a way to fix this without modifying the password?

### What is the expected behaviour?

### How to reproduce the issue?

1. create a password with special characters
2. Include as a separate variable, and interpolate the entire connection string

### Screenshots or Screencast
![Capture](https://github.com/hasura/graphql-engine/assets/118403025/155ea95a-98e4-4f9e-8a05-dd42b4995750)
![Capture2](https://github.com/hasura/graphql-engine/assets/118403025/94d4a371-3eb5-4b0d-be8f-10d1d1f4acd2)

### Please provide any traces or logs that could help here.

### Any possible solutions/workarounds you're aware of?

### Keywords

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.