op-service: Add optional headers to the signer client #12407
Merged
+66
−5
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.
Description
This adds a new flag to the signer client
HEADERS
which will provide a set of headers to pass to the remote signer.This also modifies the TLSConfig to better handle enabling TLS. Previously
TLSConfig.TLSEnabled()
would alway return true because it would default every value duringReadCLIConfig
. NowTLSConfig.TLSEnabled()
only returns true if any of the flags are set.Tests
Unit tests for flag parsing.