4
description: A URL to a tarball of the code
8
A list of code deployment URLs to keep around. Any versions found locally
9
not in this list will be removed.
13
description: The root directory the service will be installed in
18
YAML list of additional installation sources, as a string. The number
19
of install_sources must match the number of install_keys. For
23
- "cloud:precise-proposed/folsom"
24
- "http://example.com/repo precise main"
29
YAML list of GPG keys for installation sources, as a string. For apt
30
repository URLs, use the public key ID used to verify package
31
signatures. For other sources such as PPA, use null. This
32
list must have the same number of elements as install_sources, even
33
if the key items are all empty string. An example to go with the
34
above for install_sources:
42
description: "List of extra packages to add (' ' separated)."
46
description: "The worker script to run as a service. Can include paths relative to local bzr directory"
51
base64 encoded string to hold configuration information for the unit.
52
The contents will be written to a file named
53
<install_root>/<unit>/unit_config
54
where <unit> is the location the branch is extracted to.
59
description: The username to run the lander under
63
description: The group to run the lander under
65
# required for rabbitmq-server charm:
69
description: The user to log into the rabbitMQ server.
73
description: The vhost in the rabbitMQ server.