Akita Noek e531bc67e4 Better control what JT admins are allowed to do
This addresses #1981 which says that JT admins can make modifications to
a job template freely if they're just changing non functional things
like name, description, forks, verbosity, etc, while requiring them to
have access to all functional components if they're going to make any
changes to the functionality - in specific, any changes to the
inventory, project, playbook, or credentials requires that the user have
the appropriate use access on all of those things in order to make the
change.
2016-05-26 14:39:16 -04:00
2016-05-13 12:01:54 -04:00
2015-07-27 10:19:14 -04:00
2016-02-01 18:37:56 -05:00
2016-05-09 09:17:58 -04:00
2015-02-06 09:47:41 -05:00
2015-06-12 11:54:22 -04:00
2016-03-04 16:19:00 -05:00
2015-06-11 16:10:23 -04:00
2016-05-12 09:21:13 -04:00
2016-02-04 14:32:40 -05:00
2016-04-06 14:28:34 -04:00

Build Status Requirements Status

Ansible Tower

Tower provides a web-based user interface, REST API and task engine built on top of Ansible.

Resources

Refer to CONTRIBUTING.md to get started developing, testing and building Tower.

Refer to setup/README.md to get started deploying Tower.

Refer to docs/build_system.md for more about Jenkins and installing nightly builds (as opposed to running from source).

Refer to docs/release_process.md for information on the steps involved in creating a release.

Refer to http://docs.ansible.com/ansible-tower/index.html for information on installing/upgrading, setup, troubleshooting, and much more.

Description
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.
Readme 429 MiB
Languages
Python 97.8%
Jinja 0.9%
Makefile 0.5%
Shell 0.3%
HTML 0.2%
Other 0.2%