lp:~juju-jitsu/charmworld/trunk

Created by Kapil Thangavelu on 2012-07-20 and last modified on 2013-10-30
Get this branch:
bzr branch lp:~juju-jitsu/charmworld/trunk
Members of Juju-Jitsu Hackers can upload to this branch. Log in for directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Juju-Jitsu Hackers
Project:
charmworld
Status:
Development

Recent revisions

433. By Abel Deuring on 2013-10-30

heartbeat: Checks added that the bundles collection is not empty, that all MongoDB collections exist; show size of ingest queues.

Approved by Juju Gui Bot, Curtis Hovey.

432. By Benji York on 2013-10-30

Fix bug 1229179 by adding a correct route.

R=bac
CC=
https://codereview.appspot.com/19430043

431. By Aaron Bentley on 2013-10-25

Remove 018 migration; before an exodus and already deployed to production.

Approved by Juju Gui Bot, Brad Crittenden.

430. By Benji York on 2013-10-25

Add handling for "-HEAD" revisions to API2

R=bac
CC=
https://codereview.appspot.com/16950043

429. By Brad Crittenden on 2013-10-24

Add changelog to bundle page.

R=benji
CC=
https://codereview.appspot.com/16690043

428. By Brad Crittenden on 2013-10-23

Fix ingest KeyError for 'branch_deleted'.

R=
CC=
https://codereview.appspot.com/16240044

427. By Benji York on 2013-10-23

Add recent bzr changes to bundles.

R=bac
CC=
https://codereview.appspot.com/15100046

426. By Richard Harding on 2013-10-22

Refactory the proof api to be it's own module.

- Break out the proof api bits into a new api module vs the same api file.
- Move tests and fix to match
- Remove the model in the lib bits and try to keep things in views/models.

Approved by Juju Gui Bot.

424. By Richard Harding on 2013-10-18

Add charm config proofing and update api response

- Move proof logic into a new lib/proof.py module
- Update the proof api call to look through the bundles and proof them
- Change errors to be catchable exceptions, the exception contains both a msg
and debug_info we expose via the api call
- Update the api call to provide a summary error_messages (for Marco's needs)
but keep the details in the actual list of errors with the messages and the
debug info we have that went into those errors.

Sample proof api call and response:
http://paste.mitechie.com/show/1049/

Note: this is only adding the new proof checks of validating the
config/options from the charm found in the database to the options defined in
the bundle.

- Validate the option exists in the charm we found in the db
- Validate that the type is of the correct type.
- Validate that the charm we found has options at all.

QA
---
You have to ingest the charms so that we can validate them. You can then toss
the yaml file (as a single string) to the proof api endpoint as a POST'd key
deployer_file. Right now it only handles yaml.

R=
CC=
https://codereview.appspot.com/14789043

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.