Document Best Practices for Using Secrets

Open
#549 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Tech stack
r, sql
Domain
databases, documentation, security

Research direction

No documentation file or test is named. Search the repository for the @connect syntax and environment-variable handling, then document the supported way to provide secrets without putting a password in a plain-text connection string; done means a user can follow the instructions for the shown example.

Written by the indexing model from the issue text.

Description

documentation

@juliasilge is the bomb and has brought me from 0-99 with ggsql!!
Need to finish that last 1.

My connection string has a secret in it:

-- @connect: odbc://DSN=StateDW;UID=DW;PWD=******

I would rather not need to put that password in a plain text file for ggsql to be able access it. Is there documentation on how to give it access to secrets, such as a key in my R environment?

Thanks!!

Dominant language
Rust
Stars
554
Forks
30
Avg merge
17h 27m
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from posit-dev/ggsql

All issues in posit-dev/ggsql

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.