Defining ACLs in pg_hba.conf #20
Merged
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
|
@cprice-puppet, sorry about that Chris. All PL FTEs should now have permissions (team added). Fire away! |
cprice404
added a commit
that referenced
this pull request
Oct 29, 2012
Defining ACLs in pg_hba.conf
cegeka-jenkins
pushed a commit
to cegeka/puppet-postgresql
that referenced
this pull request
Oct 23, 2017
Defining ACLs in pg_hba.conf
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is to allow users to define more granular ACLs in pg_hba.conf. Users can specify lists of strings to act as items in the ACLs, such as
ipv4acls => ['hostssl jdoe all 192.168.0.0/24 cert']There are IPv4 and IPv6 versions, more for organization's sake than anything else, since IPv4 and IPv6 should be able to be mixed without a problem.
The README.md file was also modified to present an example of how to define ACLs.