Document Best Practices for Using Secrets
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 554
- Forks
- 30
- Avg merge
- 17h 27m
- Merged PRs (30d)
- 8
Description
@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!!
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
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.
Assessment
- Tech stack
- r, sql
- Domain
- databases, documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100