rossoctl / rossoctl/examples

:bug:

Open
#734 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/bug stale
Dominant language
Python
Stars
11
Forks
43
Avg merge
1d 5h
Merged PRs (30d)
4

Description

Describe the bug

the log includes the secret PAT

(base) davidhadas@MacBook-Pro-3 kagenti % kubectl logs -n team1 github-tool-79c7886bb4-5ttrk
time=2026-07-19T09:03:01.529Z level=INFO msg="Using MCP Server" UPSTREAM_MCP="" mcpServerURL=https://api.githubcopilot.com/mcp/
time=2026-07-19T09:03:01.529Z level=INFO msg="Using Authorization header" initAuthHeader="Bearer github_pat_11ABAxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
...

Steps To Reproduce

This happened to me when the PAT was already obsolete, but I suspect the tool always log it.

Expected Behavior

Never log secrets

Kagenti Version

No response

Additional Context

No response

Contributor guide

Open the contributing guide

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.

Research direction

Reproduce the issue with the provided kubectl logs command for the github-tool and trace where the Authorization header is logged. Confirm the behavior with an obsolete or test PAT, then verify that logs no longer expose authorization secrets while retaining useful authentication context.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, python
Domain
security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.