morgan fainberg 6bb14c0ff6 Use correct repo for initial version check ... Use the actual repo for the initial version check of the db version when performing `db_sync --check`. Previously we always used the Legacy Repo as the repo path was not populated in the `get_init_version` function. This allowed the case where the new expand/contract/migrate repos matched the legacy repo version number, the `db_sync --check` command would assume that everything was properly up to date regardless of the version for the expand/contract/migrate repositories. This was most noticable in the case of a db not under version control. Change-Id: Id5e6f74a5ed96fdf17e2c241466897974aa5a218 closes-bug: #1844157		2019-09-16 11:27:57 -07:00
..
contract_repo	Implement resource options for roles and projects	2019-09-09 22:07:30 +00:00
data_migration_repo	Implement resource options for roles and projects	2019-09-09 22:07:30 +00:00
expand_repo	Implement resource options for roles and projects	2019-09-09 22:07:30 +00:00
migrate_repo	Revert "Blacklist bandit 1.6.0"	2019-05-14 21:09:32 +00:00
__init__.py	Safer noqa handling	2014-03-27 18:52:07 -05:00
core.py	Allow JsonBlob to accommodate SQL NULL result sets	2019-07-12 14:46:38 -04:00
upgrades.py	Use correct repo for initial version check	2019-09-16 11:27:57 -07:00