OK, great!
Quick list for reference:
{
"changed": false,
"item": "", "stat":
{
"atime": 1386281904.370964,
"ctime": 1386281904.370964,
"dev": 180969250,
"exists": true,
"gid": 0,
"inode": 106175,
"isblk": false,
"ischr": false,
"isdir": false,
"isfifo": false,
"isgid": false,
"islnk": false,
"isreg": true,
"issock": false,
"isuid": false,
"md5": "d41d8cd98f00b204e9800998ecf8427e",
"mode": 420,
"mtime": 1386281904.370964,
"nlink": 1,
"pw_name": "root",
"rgrp": true,
"roth": true,
"rusr": true,
"size": 0,
"uid": 0,
"wgrp": false,
"woth": false,
"wusr": true,
"xgrp": false,
"xoth": false,
"xusr": false}
}
On Thursday, December 5, 2013 2:11:25 PM UTC-8, senorsmile wrote:
>
> Thanks all! I had been trying to implement the "set_fact" module, but it
> sets a different variable per host. I need a global variable that is not
> tied to a specific host. So, it would end up running the last role
> multiple times.
>
> Sounds like the file and stat modules are what are going to do the trick.
> It would be nice to have the option to set a global variable, sort of like
> set_fact does, but NOT tied to any specific host, and all host plays could
> access and modify it. This would replace the need to write to disk during
> a play.
>
> Where can I get a list of all the possible parameters used with stat?
> e.g. the docs show when: p.stat.isdir is defined and p.stat.isdir ==
> true
> but I'm not sure how to run a task conditionally using stat to check for a
> file existing.
>
>
>
> On Thursday, December 5, 2013 1:45:29 PM UTC-8, Michael DeHaan wrote:
>>
>> You should probably touch a changed file on the system if something
>> changes and use when with the stat module.
>>
>> -- Michael
>>
>> On Dec 5, 2013, at 1:35 PM, senorsmile <[email protected]> wrote:
>>
>> After trying to implement this workaround, I realize that this does NOT
>> fix my issue. I need to have a single task run at the very end, if any of
>> other multiple roles have change.
>>
>> Currently, I must duplicate the handler into the multiple roles, which
>> means the handler gets run multiple times if multiple roles have changes.
>> I need it to only run once at the very end.
>>
>> Still searching for solution to OP...
>>
>> On Wednesday, December 4, 2013 2:44:40 PM UTC-8, senorsmile wrote:
>>>
>>> I have been thinking about this all wrong. I just need to set up a
>>> handler that includes the yml for the role I want, and put a notify on the
>>> tasks of the other role.
>>>
>>> If anyone has a better (more direct way from site.yml), feel free to
>>> post.
>>>
>>>
>>> On Wednesday, December 4, 2013 2:26:22 PM UTC-8, senorsmile wrote:
>>>>
>>>> I'm trying to come up with a seemingly simple logic, yet can't figure
>>>> out how to do it in ansible:
>>>>
>>>> I want to run the last role only if any previous roles have changes.
>>>>
>>> --
>> 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.
>>
>>
--
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.
