Dev should: - Autodeploy when the "latest" tag changes on dockerhub - Rebuild its database from scratch whenever a change to the "migrate-dev" tag on dockerhub is made. Stage should: - Autodeploy whenever a tag that doesn't match "latest" or "master-*" changes on dockerhub. - Rebuild its database from scratch whenever a change to the "migrate-stage" tag on dockerhub is made. The implementation of the db resets should be handled by scripts in the Balrog repo, being updated in bug 1376331.

instead of migrate-* docker tags, we're going to go with an api on the admin that is handled by nginx to tigger the db reset

Dev exists now, and auto deploys when a docker tag is uploaded named /^master-[0-9a-f]{40}$/. this differs from the original description to ensure that admin and agent change in lock step. Stage now auto deploys when a docker tag is uploaded that is not 'latest' and not /^master-/. Database rebuilds are currently planned to be triggered by hitting /__rebuilddb__ with ldap auth. This plan is in security review.

This is complete