-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pg connector pass client options #1444
Conversation
8a2131b
to
da252f1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!!!
Nice work on the UT!
@@ -23,6 +23,7 @@ type SingleUseConnector struct { | |||
connectionDetails *ConnectionDetails | |||
// databaseName is specified by the client application | |||
databaseName string | |||
options map[string]string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe CodeClimate is complaining about this... go fmt
will align the m
in map
with the s
in string
on the line above?
a51a8b6
to
5b12ac6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!!!
pg connector sends all client options in startup message. options specified in secretless config take precendence over those sent by the client
624943b
to
dd72b31
Compare
Code Climate has analyzed commit dd72b31 and detected 2 issues on this pull request. Here's the issue category breakdown:
The test coverage on the diff in this pull request is 40.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 54.7% (0.0% change). View more on Code Climate. |
Internal issue: ONYX-14961. |
pg connector sends all client options in startup message. options specified in secretless config take precendence over those sent by the client
Desired Outcome
Please describe the desired outcome for this PR. Said another way, what was
the original request that resulted in these code changes? Feel free to copy
this information from the connected issue.
Implemented Changes
Describe how the desired outcome above has been achieved with this PR. In
particular, consider:
Connected Issue/Story
Resolves #[relevant GitHub issue(s), e.g. 76]
CyberArk internal issue link: insert issue ID
Definition of Done
At least 1 todo must be completed in the sections below for the PR to be
merged.
Changelog
CHANGELOG update
Test coverage
changes, or
Documentation
README
s) were updated in this PRBehavior
Security