No description
8ecb023939
Some packages attempt to prompt the user for certain settings during installation. Thus, this parameter sets the environment variable $BATCH to 'yes', which forces package installation scripts to accept default values for these interactive prompts. This should work for all prompts that have a default value and aren't implemented through a custom script (as this variable is built into the ports/package system). FIXME: Package install should fail if it prompts and batch isn't set; currently, the install hangs indefinitely. TODO: Allow user to specify the answers to certain prompts. I (github.com/mwpher) have NOT tested this with any packages besides bsdstats. It's a small improvement, but not a complete answer to all the complexities of package installation. |
||
|---|---|---|
| cloud | ||
| database | ||
| messaging | ||
| monitoring | ||
| network | ||
| notification | ||
| packaging | ||
| source_control | ||
| system | ||
| web_infrastructure | ||
| windows | ||
| .gitignore | ||
| __init__.py | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| README.md | ||
ansible-modules-extras
This repo contains a subset of ansible-modules with slightly lower use or priority than "core" modules.
All new modules should be submitted here, and have a chance to be promoted to core over time.
Reporting bugs
Take care to submit tickets to the appropriate repo where modules are contained. The repo is mentioned at the bottom of module documentation page at docs.ansible.com.
Testing modules
Ansible module development guide contains the latest info about that.
License
As with Ansible, modules distributed with Ansible are GPLv3 licensed. User generated modules not part of this project can be of any license.