Any ideas on this?

In general what approaches do you guys use to combine infrastructure 
inventories/vars with other projects so they can use system level 
properties as needed.  Coming from puppet we typically had a project repo 
with a provisioning repo.  the provisioning repo inherited from a base 
infrastructure init.pp.  What is a good way to do something similar to this 
in ansible?  e.g. 

inventories are tied to environments (staging / production / development). 
 group vars can be used to group variables per environment.  "all" can be 
used for all properties not included in a given group.   This makes sense, 
but i would like to reuse this setup for other projects to use vars from 
this setup --- Single place for all variables partitioned prod/dev/stage 
and inherited by other projects.

Hopefully this makes more sense. 


On Wednesday, February 8, 2017 at 11:25:12 PM UTC-8, Johannes Kastl wrote:
>
> On 09.02.17 07:26 Sonny Heer wrote: 
> > Hi all, 
> > 
> > Assume a production/staging/dev multistage environment project 
> > using ansible best practices layout.  Another custom project A in a 
> > separate git repo.   
>
> Is this "custom project" another ansible project? Then linking the 
> files could be an option. 
>
> Otherwise its hard to help you unless you tell us what kind of "custom 
> project" you have. 
>
> Johannes 
>
>

-- 
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/362f7dde-ac01-4cad-a0cf-5066e86a2ffd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to