d35d7f62ec
* Add in ESXI plugin as a choice * added in vmware esxi as an inventory source * made a migration that may not be needed but will need to circle back * black formatting * linter fixes that I missed in the first commit, squash * Update esxi to use_fqcn to true * added use_fqcn on the esxi cred to true to correctly lay down collection name * add fqcn true * updated vmware esxi to use true for fqcn * Update defaults and re-order migrations * updated defaults to add correct env var to get empty * re-ordered migrations to be in line with others * Add condition to replace vmware_esxi cred * replace direct name match with vmware cred since source supports old cred * add skeleton test * quick pass, needs more * squash this * Add tests for creating inventory ESXI source * add test case to test creating an inventory with different cred type to source name * update test and linting * added correct cred return since esxi uses same cred * assert on status code * assert that we received a 204 * Added new folder for vmware_exsi and empty json file. * Corrected the misspelling of folder name to 'esxi' * fixed misspelling for `vmware_` --------- Co-authored-by: Thanhnguyet Vo <thavo@redhat.com>
AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
To install AWX, please view the Install guide.
To learn more about using AWX, view the AWX docs site.
The AWX Project Frequently Asked Questions can be found here.
The AWX logos and branding assets are covered by our trademark guidelines.
Contributing
- Refer to the Contributing guide to get started developing, testing, and building AWX.
- All code submissions are made through pull requests against the
develbranch. - All contributors must use git commit --signoff for any commit to be merged and agree that usage of --signoff constitutes agreement with the terms of DCO 1.1
- Take care to make sure no merge commits are in the submission, and use
git rebasevs.git mergefor this reason. - If submitting a large code change, it's a good idea to join the
#ansible-awxchannel on web.libera.chat and talk about what you would like to do or add first. This not only helps everyone know what's going on, but it also helps save time and effort if the community decides some changes are needed.
Reporting Issues
If you're experiencing a problem that you feel is a bug in AWX or have ideas for improving AWX, we encourage you to open an issue and share your feedback. But before opening a new issue, we ask that you please take a look at our Issues guide.
Code of Conduct
We ask all of our community members and contributors to adhere to the Ansible code of conduct. If you have questions or need assistance, please reach out to our community team at codeofconduct@ansible.com
Get Involved
We welcome your feedback and ideas. Here's how to reach us with feedback and questions:
- Join the Ansible AWX channel on Matrix
- Join the Ansible Community Forum