feat: Add support for authentication credentials in ProviderConfig #63
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.
PR Description: Add Authentication Credentials Support in ProviderConfig
Summary
This PR enhances the
ProviderConfig
by adding support for authentication credentials via a Kubernetes Secret reference. This feature allows users to securely manage theAuthorization
header for all requests made with this configuration.Changes
secretRef
field to reference a Kubernetes Secret containing the authentication token, which will be automatically included in theAuthorization
header for all requests.Example Usage
Notes
This change is backward-compatible; existing configurations remain unaffected.
Fixes #53
I have:
make reviewable test
to ensure this PR is ready for review.