ea776641f3
This is the most basic way to move the revoke migrations into the keystone core migrations path. Check to see if the migration was performed already via the extension and if so skip performing it again. Also had to delete tests in test_sql_livetest, since they were no longer valid, they were testing the revocation extension behavior. Also removed a few tests from test_sql_upgrade, they were also testing extension behaviour logic and were creating the revoke tables before the tests to create them in the common migration repo. DocImpact: Do not run the revoke extension migrations, they are now included in core and run by default Change-Id: I8a1456bef2db3b11a364f34f38d1e6494f4b0e91 Implements: bp move-extensions |
||
|---|---|---|
| .. | ||
| versions | ||
| __init__.py | ||
| migrate.cfg | ||