lp:~fwereade/pyjuju/env-constraints
- Get this branch:
- bzr branch lp:~fwereade/pyjuju/env-constraints
Branch merges
- William Reade: Pending requested
- Diff: 0 lines
Related source package recipes
Branch information
Recent revisions
- 514. By William Reade
-
set- and get-constraints now sync environments.yaml to ensure a provider can be created to work with the constraints
- 511. By William Reade
-
don't expose constraints on non-aws ec2 clouds; don't warn about legacy keys when they're still valid
- 510. By William Reade
-
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 - 509. By William Reade
-
Add get-constraints command
Takes any number of machine names, service names, and unit names; outputs
yaml-formatted dict of name:constraints (showing the full computed
constraints dict for each entity).R=hazmat
CC=
https://codereview. appspot. com/5935047 - 508. By William Reade
-
Providers are now directly responsible for their own constraints
This is really just a rearrangement of code; nothing fundamental has
actually changed, except that Constraints.from_strs is entirely gone; and
trying to construct Constraints(None, data) will no longer produce a viable
specimen.R=hazmat
CC=
https://codereview. appspot. com/5939046
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:pyjuju
