Hey Simon! For example, imagine you have an Ansible charm which inside are some php settings applied like php memory limit, and then you relate a subordinated charm to it, that creates a new php.ini with custom configurations that the project needs.
If the playbook of the subordinated charm makes a move that doesn't count with files or configurations generated by the other playbook in the main service charm, probably will result in a conflict, and errors will be shown. I was thinking in how to avoid this, leaving less customized configurations in the main charm. But!, it's difficult to know where's the limit. Cheers!, Sebas. Em 08/09/2014 12:03, "Simon Davy" <[email protected]> escreveu: > Hi Sebastian > > On 5 September 2014 18:54, Sebastian <[email protected]> wrote: > > - Subordinated charms, when and how to use it. Conflicts with Ansible > > Charms. > > Can you give more details on "Conflicts with Ansible Charms"? > > We use the ansible support in charm-helpers a lot, for both principle > charms and subordinates, and have had no problems mixing those with > non-ansible charms, so I'd be keen to hear your issues. > > Thanks > > -- > Simon >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
