Just discussing this with Liam on #juju, I guess there's a balance between parallel deployment and guaranteed safety between charms and subordinates. A middle ground could be allowing charm authors to specify a single metadata string under the name 'Conflicts', which if matched between two deploying charms ensures one runs after the other (otherwise we still get parallel deployment).
Just discussing this with Liam on #juju, I guess there's a balance between parallel deployment and guaranteed safety between charms and subordinates. A middle ground could be allowing charm authors to specify a single metadata string under the name 'Conflicts', which if matched between two deploying charms ensures one runs after the other (otherwise we still get parallel deployment).