890bba6a0e
EC2 Security Group names are unique given a VPC. When a group_name value is specified in a rule, if the group_name does not exist in the provided vpc_id it should create the group as per the documentation. The groups dictionary uses group_names as keys, so it is possible to find a group in another VPC with the name that is desired. This causes an error as the security group being acted on, and the security group referenced in the rule are in two different VPCs. To prevent this issue, we check to see if vpc_id is defined and if so check that VPCs match, else we treat the group as new. |
||
|---|---|---|
| .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.