lp:~benji/charmworld/expose-bundle-changes

Created by Benji York and last modified
Get this branch:
bzr branch lp:~benji/charmworld/expose-bundle-changes
Only Benji York can upload to this branch. If you are Benji York please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Benji York
Project:
charmworld
Status:
Merged

Recent revisions

433. By Benji York on 2013-10-23

fix test

432. By Benji York on 2013-10-23

fix test

431. By Benji York on 2013-10-23

fix lint

430. By Benji York on 2013-10-23

plubm revision details into bundles

429. By Benji York on 2013-10-23

rename a function

428. By Benji York on 2013-10-23

refactor get_changes to not return bits of a charm, but actual values

427. By Benji York on 2013-10-22

refactor find_revision_cutoff out of update_from_revisions

426. By Benji York on 2013-10-22

refactor update_from_revisions to be simpler

425. By Brad Crittenden on 2013-10-22

Parse charms with hyphens properly.

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

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)
Stacked on:
lp:~juju-jitsu/charmworld/trunk
This branch contains Public information 
Everyone can see this information.

Subscribers