# modules needed

**URL:** <https://forum.ansible.com/t/modules-needed/11394>\
**Category:** Ansible Project\
**Created:** [April 4, 2012, 8:19pm UTC](https://forum.ansible.com/t/modules-needed/11394 "2012-04-04T20:19:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Seth\_Vidal](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@Seth\_Vidal](https://forum.ansible.com/u/Seth_Vidal)\
**Post date:** [April 4, 2012, 8:19pm UTC](https://forum.ansible.com/t/modules-needed/11394/1 "2012-04-04T20:19:37Z")

</div>

I'm working through some of my puppet recipes for systems and working  
out what modules are needed for ansible to make the playbooks have  
similar solutions/feature parity.

here are the items I've found so far:

- mount file systems/fstab edits  
- copy file src fall through.

Those are the big ticket items I've found.

-sv

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [April 4, 2012, 8:28pm UTC](https://forum.ansible.com/t/modules-needed/11394/2 "2012-04-04T20:28:56Z")

</div>

What does ‘src fall through’ mean?

would it be like

src=a,b,c dest=foo

and use the first one available?

seems like we could teach the copy module that trick

I also want it to be able to do

src= dest=

to do some limited recursive copying

---

<div class="post-metadata">

**Author:** ![Seth\_Vidal](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@Seth\_Vidal](https://forum.ansible.com/u/Seth_Vidal)\
**Post date:** [April 4, 2012, 8:33pm UTC](https://forum.ansible.com/t/modules-needed/11394/3 "2012-04-04T20:33:41Z")

</div>

> What does 'src fall through' mean?
> 
> would it be like
> 
> src=a,b,c dest=foo
> 
> and use the first one available?

yes. it's a cheat i use quite often with puppet to let me have  
host-specific configs w/o resorting to some fairly awful templating  
hacks.

> seems like we could teach the copy module that trick

I agree - but I'm a bit confused how the copy module can see that from  
the remote side. I need to look at how it works a bit better, though.

> I also want it to be able to do
> 
> src=\<directory\> dest=\<directory\>
> 
> to do some limited recursive copying

copy could grow a recurse option.

-sv

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [April 4, 2012, 8:36pm UTC](https://forum.ansible.com/t/modules-needed/11394/4 "2012-04-04T20:36:52Z")

</div>

> > seems like we could teach the copy module that trick
> 
> I agree - but I’m a bit confused how the copy module can see that from  
> the remote side. I need to look at how it works a bit better, though.

Did I read that to mean it’s copying remote files to remote files, instead of local files to remote files?

copy mostly (today) is done in runner – so picking which local file to transfer is not a big problem, the remote wouldn’t have to know.

> > I also want it to be able to do
> > 
> > src= dest=
> > 
> > to do some limited recursive copying
> 
> copy could grow a recurse option.

yep.