Does so by running the edxapp role just to generate config (as
controlled by check-migrations.sh's use of the --tag) and then
the tasks in the playbook are hardcoded to always run, regardless
of the tag.  Because the edxapp play has run, the tasks have
access to the various config variables containing DATABASES
and can tell what DBs are in use.

Skip the read replica

Update readme to match the current state of things.

Include ORGANIZATIONS_API_URL_ROOT in programs defaults

This setting is used when requesting data from the LMS Organizations API.

restructure notes_api deployment

Remove almost all references to syncdb 🔥🔥🔥

Make check-migrations script exit with proper status on errors

Django 1.8 removed the syncdb command so we can no longer run it, don't
imply that we are running it in documentation/messages, also don't
provide the scripts used on devstack/sandboxes to run it since they'll
never work anyway.

Additionally - remove yet another openid workaround which is unnecesary
since the Django 1.8 upgrade.

add config for jwt auth feature flag

DEVOPS-3685 ensure tools gets the same version the mongo play installs

While fixing a downgrade from 3 -> 2 on tools, ensure this role uses the
same version the mongo_3 play uses.

OPS-1327 Allow User to specify the lifetime of the sandbox when creating

Add config for SUPPORT_URL

Max/small fixes

The "connection: local" option prevented us from running the playbook on
another host (e.g. an app server) which gets around security
restrictions on connecting to DB servers. Also, the option is totally
unnecessary. There's no reason this play couldn't run remotely.

Set better defaults for LMS_BASE, CMS_BASE

This AMI includes the fix to not clobber db perms

Fix CI by appending privileges

New AMI

remove the fail logic and add the informational message

Having an empty CMS_BASE variable causes the "View Unit in Studio" button on the LMS
to not work properly. These are better defaults.

Merge dogwood to master

Support externally hosted comprehensive themes

add s3 backend configuration settings

The old Stanford-style themes can be pulled in from an external Git
repo; no such provision was previously available for comprehensive
themes.

* Introduce two new configuration variables:
- EDXAPP_COMPREHENSIVE_THEME_SOURCE_REPO: Git repo for the
  comprehensive theme
- EDXAPP_COMPREHENSIVE_THEME_VERSION: Git branch, tag, or revision to
  check out from the repo

* Introduce a new task, "checkout comprehensive theme", doing the
equivalent of the previously existing "checkout theme" task. Check out
the theme repo to EDXAPP_COMPREHENSIVE_THEME_DIR. If
EDXAPP_COMPREHENSIVE_THEME_SOURCE_REPO is unset, continue to assume
that EDXAPP_COMPREHENSIVE_THEME_DIR already exists and is populated
with a comprehensive theme.

* Rename the "checkout theme" task to "checkout Stanford-style theme".

ECOM-3605