Seems like the cleaner way to do this is probably to just spend the time to rewrite stuff to roles. I spoke with someone locally about this, and they showed me the way they were doing it with roles. it seems like what I'm doing is very similar conceptually, but different in execution. I was looking to have central configs tagged with keywords that can then be included and only execute stuff with a certain tag.
Roles seems to accomplish this, but I can't store all the configs in one location I have to create a hierarchy of folders / etc. And that's not the worst solution in the world, just different. thanks for everyones help!! :) (I still think being able to include and execute only certain tags from that include :) ) On Tuesday, December 3, 2013 8:42:54 AM UTC-5, C. Morgan Hamill wrote: > > Excerpts from BrianAI's message of 2013-12-03 06:08:08 -0500: > > Yes, that much I knew / figured after reading and experimenting. > > > > So other that using that as a variable to call in the cron.yaml file > > (which I think you referred to as a messy hack), is there anyway to > > achieve the desired results? > > > > The goal is to include a yaml but filter which jobs to run on that > include. > > You'll have to "fake it" by picking a variable name and testing on it > for each task. > > - debug: msg="this is probably a task" > when: "'jam_master_jay' in cron_tags" > > -- > Morgan Hamill > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
