mirror of
https://github.com/ZwareBear/awx.git
synced 2026-03-20 07:43:35 -05:00
b34adcb10d
We recently made AWX_ISOLATED_PRIVATE_KEY and AWX_ISOLATED_PUBLIC_KEY read-only so that they're not inadvertently modified and/or deleted (which would cause isolated task execution to break). Tower's notion of a read-only setting, though, is really more like "hard-coded in a .py file". What we really need is support for settings that are not user configurable/changeable, but that we still want to display to users from the DB. In leiu of a complicated change to `awx.conf.settings`, this change provides special support to these two settings so they behave in the manner we expect. see: https://github.com/ansible/ansible-tower/issues/7375
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.