nais postgres proxy bør ha maskinlesbar output
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 57/100
Research direction
Start by locating the nais postgres proxy command and reading how it currently assembles its connection details and prints the human-readable output. The issue suggests an optional machine-readable mode, such as environment variables, and asks to use PostgreSQL’s standard variables where possible. Done means the command can emit the connection details in a form a program can consume; the issue does not name a file or test.
Written by the indexing model from the issue text.
Description
nais postgres proxy ingtest-1 --reason "all your db are belong to kimtore" --ttl 1h --access-level admin
Gir følgende output:
Postgres access ready.
Postgres relay listening at 127.0.0.1:55541; user: [email protected]; TLS server name: pg-ingtest-1-main-9ff1f921-rw.dataplattform.svc.cluster.local; CA: /var/folders/m8/8z4wwnrd4tbbm9n6kz8992mc0000gn/T/nais-postgres-ca-263561047.crt
Use host= hostaddr= sslmode=verify-full sslrootcert=. For automatic setup use 'nais postgres psql'.
Database password is only available here with --print-password (sensitive output).
Jeg lager et program som skal koble seg til denne databasen, det hadde derfor vært svært nyttig med maskinlesbar output fra denne kommandoen. Gjerne som environment-variabler til standard output. Kanskje switche mellom denne typen output og menneskelig output med et flagg?
Eksempel, bruk gjerne Postgres sine egne miljøvariabler der det er mulig:
PGPASSWORD=oensutheoUNTH5R6Ce
[email protected]
PG_CA_PATH=...
PG_KEY_PATH=...
PG_CERT_PATH=...
# og så videre
- Dominant language
- Go
- Stars
- 2
- Forks
- 5
- Avg merge
- 3h 49m
- Merged PRs (30d)
- 34
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 nais/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
-
mcp: mock schema is invalid GraphQL, so schema_* tests pass on a parse errorPossibly taken @Starefossen claimed this 2 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
mcp: schema_list_queries returns an array as structuredContent, and its outputSchema is invalidPossibly taken @Starefossen claimed this 2 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
Similar issues
-
automation doc-healer documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Anthropic /v1/messages: only the last thinking block of an assistant message is keptPossibly taken @Shayan12456 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ollama/ollama#19415 · 1 comment ·
Maintainers usually reply within 1 day
-
area:recipes event:contribfest format:human-first source:agent status:needs-triage type:recipe
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
cadence-workflow/cadence-ai-samples#140 ·
Maintainers usually reply within 1 day
-
customer issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dolthub/doltgresql#3716 ·
Maintainers usually reply within 1 day
-
ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
evcc-io/evcc#35605 · 1 comment ·
Maintainers usually reply within 1 day