-
Notifications
You must be signed in to change notification settings - Fork 144
VMware: Best Practices
New modules are already well sanity checked. As existing modules are updated, we expect significant changes to also include meeting of the sanity checks.
Changes for existing modules would be:
- Meet the Module Developer Checklist - https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_best_practices.html
- Pass the Ansible test suite -
- python coding standard
- documentation expectations
- Make better use of built in functions for argument checking
- Have integration tests
- Work with
--check
(check mode). - Have a look at the vmware module_utils and reuse as many of the existing methods there.
- Look at other modules for examples on how to include existing documentation and existing module arguments
- Follow the standard module parameters
This Wiki is used for quick notes, not for support or documentation.
Working groups are now in the Ansible forum
Ansible project:
Community,
Contributor Experience,
Docs,
News,
Outreach,
RelEng,
Testing
Cloud:
AWS,
Azure,
CloudStack,
Container,
DigitalOcean,
Docker,
hcloud,
Kubernetes,
Linode,
OpenStack,
oVirt,
Virt,
VMware
Networking:
ACI,
AVI,
F5,
Meraki,
Network,
NXOS
Ansible Developer Tools:
Ansible-developer-tools
Software:
Crypto,
Foreman,
GDrive,
GitLab,
Grafana,
IPA,
JBoss,
MongoDB,
MySQL,
PostgreSQL,
RabbitMQ,
Zabbix
System:
AIX,
BSD,
HP-UX,
macOS,
Remote Management,
Solaris,
Windows
Security:
Security-Automation,
Lockdown
Tooling:
AWX,
Galaxy,
Molecule
Plugins:
httpapi