nebari-dev / nebari-dev/data-science-pack
[ENH] - Investigate credential management solutions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 7
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 13
Description
Feature description
On JHub, users want to be able to store credentials securely. The primary use case for this is Github/Gitlab credentials. There are other places where this would be helpful like for private nebi packages (so we don't have to store PATs in the pixi.toml).
I'd like to investigate what the options are for handling this properly.
Value and/or benefit
Users are not required to store their credentials in plain text on the system OR have to enter credentials in the CLI for every push/pull.
Anything else?
No response
Contributor guide
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 reviewing pixi.toml and the stated GitHub/GitLab credential use cases. Compare secure credential-management options and document a recommendation that avoids plaintext credentials and repeated CLI entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, gitlab
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100