lp:~fwereade/pyjuju/block-legacy-constraints-usage

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:~fwereade/pyjuju/shadow-trunk-1204 at revision 513

William Reade: Pending requested 2012-03-29

Diff: 125 lines (+54/-1)

5 files modified

juju/control/constraints_set.py (+4/-1)
juju/control/deploy.py (+1/-0)
juju/control/legacy.py (+15/-0)
juju/control/tests/test_constraints_set.py (+13/-0)
juju/control/tests/test_deploy.py (+21/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

519. By William Reade on 2012-03-30

merge parent

518. By William Reade on 2012-03-30

merge parent

517. By William Reade on 2012-03-29

merge parent

516. By William Reade on 2012-03-29

code tidying after post-sleep self-review

515. By William Reade on 2012-03-29

block attempts to use constraints in legacy deployments

514. By William Reade on 2012-03-29

set- and get-constraints now sync environments.yaml to ensure a provider can be created to work with the constraints

513. By William Reade on 2012-03-29

implement env constraints

512. By William Reade on 2012-03-28

unused import

511. By William Reade on 2012-03-28

don't expose constraints on non-aws ec2 clouds; don't warn about legacy keys when they're still valid

510. By William Reade on 2012-03-28

Implement maas-name constraint

Descended from lp:~julian-edwards/juju/name-constraints; but uses new-style
constraints registration.

Also uses a custom ubuntu-series constraint to forbid use of charms written
for systems we can't yet provision with MAAS.

R=allenap, hazmat
CC=
https://codereview.appspot.com/5938050