Thanks for the feedback guys. I think, as James suggested, the simplest way would be to download all the assets in a separate role.
That sayid, I was hoping to download / sync to the asset server in an addhock fashion in various roles. To do that I think it would be easier to write a custom module than piecing together a long list of calls to standard modules every time I need an asset. As an example, I'm thinking something like this would be good: tasks - name: download asset and sync to asset server url: http://www.some.com/asset.tar.gz dest: /var/assets asset_host: [email protected] This would download the asset if if doesn't exist on the asset server and syncronise with the local file system. The dest directory could be mirrored between the asset server and the host machine. -- 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/b957ea02-777a-431c-b494-08070037b32c%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
