I played with this by deploying the branch-source-builder from our trunk with a small change like:
=== modified file 'juju-deployer/branch-source-builder.yaml' --- juju-deployer/branch-source-builder.yaml 2013-12-19 17:11:55 +0000 +++ juju-deployer/branch-source-builder.yaml 2014-01-26 21:46:10 +0000 @@ -20,6 +20,7 @@ options: branch: lp:ubuntu-ci-services-itself main: ./branch-source-builder/run_worker + unit-config: include-base64://configs/unit_config.yaml bsb-rabbit: branch: lp:~canonical-ci-engineering/charms/precise/ubuntu-ci-services-itself/rabbitmq-server charm: rabbitmq
I think this is what you guys were wanting, right?
This is config format agnostic which is probably useful. I did YAML locally, but the charm doesn't care.
« Back to merge proposal
I played with this by deploying the branch- source- builder from our trunk with a small change like:
=== modified file 'juju-deployer/ branch- source- builder. yaml' branch- source- builder. yaml 2013-12-19 17:11:55 +0000 branch- source- builder. yaml 2014-01-26 21:46:10 +0000
options:
branch: lp:ubuntu-ci-services-itself
main: ./branch- source- builder/ run_worker base64: //configs/ unit_config. yaml
bsb-rabbit:
branch: lp:~canonical-ci-engineering/charms/precise/ubuntu-ci-services-itself/rabbitmq-server
--- juju-deployer/
+++ juju-deployer/
@@ -20,6 +20,7 @@
+ unit-config: include-
charm: rabbitmq
I think this is what you guys were wanting, right?
This is config format agnostic which is probably useful. I did YAML locally, but the charm doesn't care.