They made large changes in the callback code in 2.0->2.1
http://docs.ansible.com/ansible/latest/porting_guide_2.0.html#callback-plugins

I tested a few tweaks to make this run, but because it's the old v1
version, we're looking at a mostly complete rewrite.  Deleting it
and deciding if we actually valued this output was easier.

We've decided not to re-enable callbacks since all this output is in our
CI/CD and having it in hipchat isn't needed.

add docker/plays files to list of changed files

[ENT-486] Add `ENTERPRISE_SUPPORT_URL` variable.

Aali/ops 2209 upgrade sandbox mongo role

This is needed because there is a race condition between the stop and
start of supervisor.  The stop will not wait for all child process to
have shutdown by design because this behavior is needed for lms workers.

This means that when we try to do a stop and start together, and the first process
has not fully stopped, we get a failure in the startup of the second process.

There is no obvious way to deal with this in systemd so dealing with it here
instead.

This is needed so that we can properly build devstacks without passing in any other config.

WIP: script to make API call to get cache hit rate

Upgrade mongo agent

Don't source the ruby env before running bundler

`retries` don't work without `until`

The `retries` statement is just ignored unless an `until` clause
is provided.

https://github.com/ansible/ansible/issues/20802

* Add OAUTH_DELETE_EXPIRED to LMS Envs
* Adding comments and CHANGELOG entry

Nothing seems to be using this module.

And it's written in the old ansible module style.

This cleans up a warning about wait being defined twice in this task

allow custom blacklist rules for splunk forwarder

  [WARNING]: While constructing a mapping from /var/lib/go-agent/pipelines
  /loadtest-
  credentials/configuration/playbooks/continuous_delivery/launch_instance.yml,
  line 68, column 7, found a duplicate dict key (wait). Using last defined value
  only.

Include the Environment-Deployment when announcing an AMI build

Otherwise, we see 3 edxapp AMI builds per gocd pipeline, but have
no idea which one is which.  Similar issue for IDAs where you get at
least 2 AMIs.

We get S3 timeouts a few times a week

Retry if we can't get to github.

We sometimes can't get to github because of intermittent network issues. We should
try a few times before we declare it a failure.

Use ansible core module ec2_ami

Be able to configure the analytics dashboard name.

This message is no longer useful.

Disable what we can and move on for now.

Some AMIs are missing the 'apt-daily-upgrade.timer' job and are failing.

See OPS-2365

It was more useful previously when we were monitoring the pipelines more closely but
is now just treated as noise in chat.