Add ability to pass TLS certs and keys inline #349
Merged
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.
What this PR does:
With prometheus/exporter-toolkit#158, it is now possible to pass forward TLS certificates and keys inline as part of the
TLSConfig
for the Server.This PR also extends the
TLSConfig
withinServer.go
to allow the TLS certificate, private key and client CAs to be passed inline as a string. The content of this string is expected to be exactly the same as a file, a PEM-encoded sequence of bytes. All parameters are then passed forward toweb.TLSConfig
withinprometheus/exporter-toolkit
as before.Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]