feat: add support for custom authorization header names#2524
feat: add support for custom authorization header names#2524Ndugu2 wants to merge 1 commit intokubernetes-client:masterfrom
Conversation
Signed-off-by: Kosea Kalema <koseakalema2@gmail.com>
|
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Ndugu2 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR adds the ability to use custom authorization header names in the Kubernetes Python client. Currently, the client hardcodes "Authorization" as the header name, which prevents users who need custom headers (e.g., "MY-AUTH-TOKEN") for security compliance.
Changes:
authorization_headerconfig option (defaults to "Authorization")auth_settings()to use configured header nameWhich issue(s) this PR fixes:
Fixes #2510