SpecterOps / SpecterOps/Nemesis
Hasura not deployed if POSTGRES pwd contains @
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 997
- Forks
- 104
- PR merge metrics
- No merged PRs in 30d
Description
If "@" is used in the POSTGRES_PASSWORD, the hasura failed to build. Probably caused by using @ as the user/host delimiter.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Hasura deployment with a POSTGRES_PASSWORD containing "@" and inspect the configuration or build entry point that assembles the database connection value. Done means deployment succeeds with that password and the existing deployment checks, if present, still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100