Merge ~cjwatson/launchpad-layers:rabbitmq-optional-relation into launchpad-layers:main
Proposed by
Colin Watson
Status: | Merged |
---|---|
Merged at revision: | 7287e67e5435d7567abf74c411d5ead7d58a3420 |
Proposed branch: | ~cjwatson/launchpad-layers:rabbitmq-optional-relation |
Merge into: | launchpad-layers:main |
Diff against target: |
84 lines (+35/-14) 2 files modified
launchpad-base/config.yaml (+5/-0) launchpad-base/reactive/launchpad-base.py (+30/-14) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Guruprasad | Approve | ||
Review via email: mp+439193@code.launchpad.net |
Commit message
Allow non-relation-driven RabbitMQ configuration
Description of the change
This makes it easier to migrate a non-charmed Launchpad environment to a charmed deployment: everything in a given environment should use the same RabbitMQ server, so we probably want to start by using the existing one rather than demanding that the broker URLs be provided using a Juju relation.
To post a comment you must log in.
LGTM 👍🏼