This commit adds playbooks and files necessary to do local development
from within Vagrant.
These playbooks start with a fresh Ubuntu 12.04 machine and:
- Install Ansible
- Install the Tower nightly
- Install all components to exactly mirror production, except Apache
- Install uwsgi and nginx for local development (since Apache lacks a
working auto-reload)
This isn't entirely perfect -- in particular, developing on task code
is probably challenging until I figure out how to get celery not to
read from the install, but it is a very easy way to get 90% of the way
there very, very quickly.
Since we're not refreshing the list of projects after submission of an update request, the UI does not have the most recent update ID in memory. Before launching the log viewer dialog it now requests the latest project record from the API and initializes with the correct ID.
Now the dialog only appears on job template save when the host config key or URL actually change. Before the dialog always appeared when allow callbacks was enabled.
If playbook submission fails, check for a 400 status and parse the key/value pairs returned by the API. This occurs on an attempt to submit a job template that is no longer valid. Fixed JS compile errors from prior commit.
Reload the list of tasks whenever a play is selected. Fixed search cancel. Streamlined initial load process so that it shares as much of the event processing code as possible.
This commit adds three files to .gitignore, to support local development
using Vagrant VMs.
Regarding `awx/main/fixtures`: This is to allow for a dev's primary user
to be in a fixture, so it's easily loaded.
Calculating initial container heights and rowsize on the inventory page was not working correctly on first page load. Issue was misalignment of function declaration and injector. Also needed to add e.stopPropagtion() call in the search helper. Without it the group search refresh gets called multiple times whenever the host list is refreshed.
Happening on response to Delete prompt. Removed modal hide listener when starting spinner. Not sure why I thought that was needed. Instead, just close the dialog and start the spinner. If an error occurs, ProcessErrors always stops the spinner. Issue was caused by a race condition. ProcessErrors would sometimes fire tht stop before the event listener fired a start.
Includes commits from release_1.4.11 branch up to and including d434e675a7c9727af900d7c21de5e542aef0eb98. That should be everything. What remains is testing.
