I wouldn't do this. You're playbooks should be very explicit. Are you just
trying to reduce the number of playbooks you have in your directory?
On Tuesday, October 14, 2014 11:14:58 PM UTC-7, Denis J. Cirulis wrote:
>
> Hello,
>
> let's suppose I have multiple groups of virtual guests, all are split to
> different environments and are running 2 kinds of applications but with
> different configurations.
> In /etc/environment there env variables APPENV and APPNAME which contain
> belonging to env like
> APPENV=test,APPENV=stage,APPENV=dev,APPNAME=app1,APPNAME=app2 and so on.
> There is one common role 'common' where all the provisioning and initial
> configuration tasks and files are stored (this works good).
> I want to populate roles list in top main.yml playbook with registering
> these env variables as Ansible vars and use it in
>
> roles:
> - { common }
> - { $appenv_$appname }
>
> Is it normal or I do have to think of something different ?
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/3eb96010-6f53-4e04-8d8a-089b71d6c493%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
