The proposal to rename --constraints to --model-constraitns is for clarity. After bootstrap, these constraints on the model are manipulated by set-model-constraints and get-model-constraints command. The problem at the moment is the consistent terminology.
Note that these commands are not new and have existed in Juju for a while.
@Peter Matulis (petermatulis) ,
I am surprise to hear that application constraints as a concept is news to you. How do you look up constraints now? Both set-constraints and get-constraints commands in Juju take an application as a mandatory argument.
@Richard Harding (rharding),
The proposal to rename --constraints to --model-constraitns is for clarity. After bootstrap, these constraints on the model are manipulated by set-model- constraints and get-model- constraints command. The problem at the moment is the consistent terminology.
Note that these commands are not new and have existed in Juju for a while.
@Peter Matulis (petermatulis) ,
I am surprise to hear that application constraints as a concept is news to you. How do you look up constraints now? Both set-constraints and get-constraints commands in Juju take an application as a mandatory argument.