# The Pull Paradigm

**URL:** <https://forum.ansible.com/t/the-pull-paradigm/12561>\
**Category:** Ansible Project\
**Created:** [March 23, 2013, 2:40am UTC](https://forum.ansible.com/t/the-pull-paradigm/12561 "2013-03-23T02:40:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brian\_Stinson](https://avatars.discourse-cdn.com/v4/letter/b/43a26b/32.png) [@Brian\_Stinson](https://forum.ansible.com/u/Brian_Stinson)\
**Post date:** [March 23, 2013, 2:40am UTC](https://forum.ansible.com/t/the-pull-paradigm/12561/1 "2013-03-23T02:40:49Z")

</div>

Greetings!  
I’ve been a long time lurker on the list, and just started deploying with Ansible at ${WORK}. I was wondering if there is any interest in expanding the pull paradigm, and how one might help with that. I spent a few minutes creating a new transport called “pull” that right now is pretty much copied from local, but exposes ansible facts to be used to limit execution to the current host (my use-case involves hostname, fqdn, and ipv4\_addresses). I haven’t tested much yet, but [https://github.com/tabashco/ansible/tree/pull-transport](https://github.com/tabashco/ansible/tree/pull-transport) has a few lines to start.

–Brian

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [March 23, 2013, 3:34pm UTC](https://forum.ansible.com/t/the-pull-paradigm/12561/2 "2013-03-23T15:34:46Z")

</div>

Interesting, though I wonder if there's a way to do this in the local  
transport instead, to avoid creating another transport?

There's also another open PR about upgrading ansible-pull itself, that  
I've yet to review, that aims to do similar by slightly different  
means.

Curious as to your thoughts on it.