Merge lp:~matsubara/charms/precise/oops-tools/trunk into lp:charms/oops-tools
Proposed by
Diogo Matsubara
Status: | Merged |
---|---|
Merged at revision: | 12 |
Proposed branch: | lp:~matsubara/charms/precise/oops-tools/trunk |
Merge into: | lp:charms/oops-tools |
Diff against target: |
200 lines (+134/-10) 7 files modified
.bzrignore (+1/-0) README.txt (+7/-0) config.yaml (+33/-0) hooks/amqp-relation-changed (+62/-0) hooks/db-relation-changed (+12/-10) hooks/db-relation-joined (+16/-0) metadata.yaml (+3/-0) |
To merge this branch: | bzr merge lp:~matsubara/charms/precise/oops-tools/trunk |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Clint Byrum (community) | Needs Fixing | ||
Review via email: mp+112017@code.launchpad.net |
Commit message
Add basic README, support to use amqp and list Diogo Matsubara as the maintainer of the charm.
Description of the change
Hi,
this branch adds a README file, myself as the maintainer and support to use an amqp queue.
charm proof doesn't return anything, so I think it's free of lint.
Cheers,
Diogo
To post a comment you must log in.
Diogo, this does not look right.
I see config-get's mixed with relation-get's in db-relation- changed/ joined.
There is a rabbitmq charm, so I'd like to see a rabbitmq relation in addition to the config.yaml values for the external AMQP server.
Also the check for empty relation values seems to have been removed in db-relation- changed, which may cause race conditions since we may run that hook before the database server has set the values we want.