added functions for setting ApiKey and Authorization Headers #41
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 kind of change does this PR introduce?
I removed the function
TokenAuth
, withSetApiKey
andSetAuthToken
, so that users can change the apiKey and authorization headers individually.What is the current behavior?
Currently TokenAuth sets the apiKey and authorization header
What is the new behavior?
postgres.SetAuthToken( authToken string)
will set the authorization header for subsequent request andpostgres.SetApiKey( apiKey string)
will set the apiKey header for subsequent request