I'm guessing this is just a minor oversight that needs to be cleaned up, however its worth mentioning that some of the functionality converted to action_plugins still remain as modules in library/.
Somewhat relatedly to this topic, do action_plugins require a file (even if empty) in library/ such as fetch?
<tim/>
This is really an internals question that users shouldn't have to think about.
There's no "oversight" either.
Currently the assemble module doesn't use the daisy chain return logic
that "get_url" uses, so it still has a server side module.
The files in the modules directory when they are basically present are
there because sometimes they ARE needed, and otherwise someone
browsing the source code can quickly see all of the modules that are
available and read the source to know which ones are implemented
server side.
Sorry. It's Monday and I'm feeling dense.
This is really an internals question that users shouldn't have to think about.
Understood. I'm writing an action plugin of my own.
There's no "oversight" either.
So Ansible doesn't necessarily check if a server side plugin was a file in library/.
Currently the assemble module doesn't use the daisy chain return logic
that "get_url" uses, so it still has a server side module.
I see. That just needs to be cleaned up then.
The files in the modules directory when they are basically present are
there because sometimes they ARE needed,
and their need is a matter of implementation? A module that needs to perform a server side operation and a remote one per host.
and otherwise someone
browsing the source code can quickly see all of the modules that are
available and read the source to know which ones are implemented
server side.
Got it.
<tim/>