This repository has been archived by the owner on Jul 14, 2021. It is now read-only.
Allow Pushy Server to optionally use a different username for establishing database connections #190
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e used for connecting to the DB vs in DB queries Signed-off-by: Zane Geiger <[email protected]>
… connections with corresponding connection user attribute Signed-off-by: Zane Geiger <[email protected]>
Signed-off-by: Zane Geiger <[email protected]>
zanecodes
force-pushed
the
connection-user
branch
from
6bfac5b to
648bb23
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 change allows Pushy Server to optionally use a different username for establishing database connections than is used within database queries. This is necessary when using Azure Database for PostgreSQL as an external database.
Issues Resolved
chef/chef-server#1559
Check List