open-telemetry / open-telemetry/weaver
Support passing github credentials if remote repository requires authentication
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 486
- Forks
- 108
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 40
Description
Is your feature request related to a problem? Please describe.
I'm trying to use weaver's -r option to point to a repository that is hosted on github.com but via an enterprise account requiring authentication. When generating artifacts it prompts for username and password, which prevents the tool from being used in automation pipeline directly (needs to wrap it around something like tmux)
Describe the solution you'd like
a way to pass credentials (username and password) so repositories can be accessed: specific environment variables or CLI args would be good
Describe alternatives you've considered
I've tried authenticating via gh auth login, adding git config credential.helper , setting GITHUB_TOKEN env var, but i still run into the prompt
Wrapping the weaver command around tmux works.
tmux new-session -d -s "weaver" "weaver registry generate -r https://github.com/<path-to-repository> ..."
tmux send-key -t weaver: $GHEC_USER "Enter"
tmux send-key -t weaver: $GHEC_PASS "Enter"
But this feels an extra step that could be removed.
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 at the weaver registry generate command and trace how the -r repository URL is accessed and how authentication prompts are handled. Review the existing GitHub and credential behavior described in the issue, then define a non-interactive credential path that works for automation and verify that authenticated repositories no longer prompt during generation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- authentication, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100