Merge lp:~stub/charms/precise/postgresql/bug-1187508-allowed-hosts into lp:charms/postgresql
Proposed by
Stuart Bishop
Status: | Merged |
---|---|
Merged at revision: | 57 |
Proposed branch: | lp:~stub/charms/precise/postgresql/bug-1187508-allowed-hosts |
Merge into: | lp:charms/postgresql |
Prerequisite: | lp:~stub/charms/precise/postgresql/charm-helpers |
Diff against target: |
52 lines (+13/-0) 2 files modified
README.markdown (+4/-0) hooks/hooks.py (+9/-0) |
To merge this branch: | bzr merge lp:~stub/charms/precise/postgresql/bug-1187508-allowed-hosts |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Marco Ceppi (community) | Approve | ||
Review via email: mp+174771@code.launchpad.net |
Description of the change
This is a resubmission of https:/
This is to address Bug #1187508, where a client charm has no way of knowing if the credentials it has will actually work for it yet.
Simple change to set and export an "allowed-units" relation setting. This will show if you can connect to the database or not. Since the relations run asynchronously, there is no way to determine this otherwise. If your host is in the allowed_host setting, your client IP has been added to the hba conf file.
To post a comment you must log in.
The new relation setting can be tested with https:/ /code.launchpad .net/~stub/ charms/ precise/ postgresql- psql/trunk/ +merge/ 174773