Merge lp:~jorge/juju-core/bundle-docs into lp:juju-core/docs

Proposed by Jorge Castro
Status: Merged
Approved by: Nick Veitch
Approved revision: no longer in the source branch.
Merged at revision: 186
Proposed branch: lp:~jorge/juju-core/bundle-docs
Merge into: lp:juju-core/docs
Diff against target: 12 lines (+2/-0)
1 file modified
htmldocs/charms-bundles.html (+2/-0)
To merge this branch: bzr merge lp:~jorge/juju-core/bundle-docs
Reviewer Review Type Date Requested Status
charmers Pending
Review via email: mp+197422@code.launchpad.net

Description of the change

Add config review as part of the bundle process.

To post a comment you must log in.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'htmldocs/charms-bundles.html'
2--- htmldocs/charms-bundles.html 2013-11-25 17:59:24 +0000
3+++ htmldocs/charms-bundles.html 2013-12-02 17:27:59 +0000
4@@ -143,6 +143,8 @@
5
6 <p>After you have created the bundles.yaml and readme, you need to proof the bundle to make sure it is valid. You can push them to your namespace, the Juju Charm store will automatically find your bundle and index it in the store. Ensure you are using your launchpad name and a unique bundle name:</p>
7
8+<p class="caution"><strong>Tip:</strong>You should review the configuration options for the charms you are planning to use in a bundle, some of them generate passwords for services or might need configuration as a separate step. This may or may not be desireable for users, so if there are any extra steps required document them in your README.md file.</strong></p>
9+
10 <pre class="prettyprint lang-bash">
11 juju bundle proof bundles.yaml
12 bzr push lp:~yourusername/charms/bundle/yourbundlename/bundle

Subscribers

People subscribed via source and target branches