connection string not being recognized
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure, postgresql, typescript
Research direction
The issue reports a failure in the action that handles connection strings; begin by reproducing it with the supplied Azure PostgreSQL string, especially the password containing leading special characters. Compare the behavior with the command-line and DBeaver connections, and consider the issue complete when that documented string is accepted without the current validation error.
Written by the indexing model from the issue text.
Description
I have a secret in the following format as per all of the documentation
psql "host='mypostgresservername1.postgres.database.azure.com' port=5432 dbname='postgres' user='myuser@mypostgresservername1' password='&&&&&&&&&' sslmode=require"
My password contains and starts with special (non alpha-numeric) characters and might also end the same way.
I have verified through connecting via the command line and DBeaver that all values are correct.
I get the following ambiguous and frustrating error:
Error: Error occurred while running action:
Error: Please provide a valid connection string. A valid connection string is a series of keyword/value pairs separated by space. Spaces around the equal sign are optional. To write an empty value, or a value containing spaces, surround it with single quotes, e.g., keyword = 'a value'. Single quotes and backslashes within the value must be escaped with a backslash
No whitespace in any of my values, nor backslashes.
Please help. This is terrible.
- Dominant language
- TypeScript
- Stars
- 25
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
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.
More from Azure/postgresql
-
need-to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/postgresql#58 ·
-
need-to-triage
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Azure/postgresql#55 ·
-
need-to-triage
Difficulty 5/5 Over a week Newbie friendliness 20/100
Azure/postgresql#53 · 1 comment ·
-
need-to-triage
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Azure/postgresql#52 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Azure/postgresql#48 · 2 comments · 2 reactions ·
All issues in Azure/postgresql
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mksglu/context-mode#1200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jaegertracing/jaeger-ui#4506 ·
-
area:desktop area:ui bug platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/claude-code#96687 ·
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
AOSSIE-Org/DebateAI#582 · 2 comments ·