User-Agent value defaults to Unknown currently for all kubeconfig token triggers. This is due to the fact that the code tries to use a normal string to access the value from the headers, whereas all keys and values in the headers dict are byte strings.
Types of changes
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
[ ] Lint and unit tests pass locally with my changes (if applicable)
[ ] I have run pre-commit (pre-commit in the repo)
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)
[ ] Linked to the relevant github issue or github discussion
Proposed changes
User-Agentvalue defaults toUnknowncurrently for all kubeconfig token triggers. This is due to the fact that the code tries to use a normal string to access the value from the headers, whereas all keys and values in the headers dict are byte strings.Types of changes
Checklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.pre-commitin the repo)Before:
After: