Use Prometheus bearer token only when provided #39
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Description
This library is used in
kube-burner
.kube-burner
'sinit
command acceptsusername
,password
andtoken
parameters for connecting to Prometheus. However, it is not possible to connect to Prometheus that is configured with username/password only because this library unconditionally sets theBearer
header, including with an emptytoken
. This results in a 401 from the Prometheus client.Related Tickets & Documents
Checklist before requesting a review
Testing
I tested this by building
kube-burner
with the proposed changes and seeing it successfully connect to my basic auth Prometheus.