de29bafc1e
AWS security groups are unique by name only by VPC (Restated, the VPC and group name form a unique key). When attaching security groups to an ELB, the ec2_elb_lb module would erroneously find security groups of the same name in other VPCs thus causing an error stating as such. To eliminate the error, we check that we are attaching subnets (implying that we are in a VPC), grab the vpc_id of the 0th subnet, and filtering the list of security groups on this VPC. In other cases, no such filter is applied (filters=None). |
||
|---|---|---|
| .github | ||
| cloud | ||
| commands | ||
| database | ||
| files | ||
| inventory | ||
| network | ||
| packaging | ||
| source_control | ||
| system | ||
| test | ||
| utilities | ||
| web_infrastructure | ||
| windows | ||
| .gitignore | ||
| .travis.yml | ||
| __init__.py | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| README.md | ||
| shippable.yml | ||
| test-docs.sh | ||
| test-requirements.txt | ||
| VERSION | ||
ansible-modules-core
This repo contains Ansible's most popular modules that are shipped with Ansible.
New module submissions for modules that do not yet exist should be submitted to ansible-modules-extras, rather than this repo.
Take care to submit tickets to the appropriate repo where modules are contained. The docs.ansible.com website indicates this at the bottom of each module documentation page.
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.
Installation
There should be no need to install this repo separately as it should be included in any Ansible install using the official documented methods.