openstack
/
keystone
Code Issues Proposed changes

Rename protocol cascade delete migration file 

Due the related bug, the file names weren't being correctly processed.
This patch renames the files to use different names accordingly to their
phases. Renaming the files also enables the possibility of removing the
migration from the data_migration banned tests.

Change-Id: I2413686cd8c89c88397fd3923fe9491015a8c534
Related-Bug: 1658116
This commit is contained in:
Rodrigo Duarte Sousa 2017-02-14 10:26:54 -03:00 committed by Rodrigo Duarte
parent 9c474958b1
commit 2b0050af20
4 changed files with 1 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

0
keystone/common/sql/contract_repo/versions/013_protocol_cascade_delete_for_federated_user.py → keystone/common/sql/contract_repo/versions/013_contract_protocol_cascade_delete_for_federated_user.py
View File

0
keystone/common/sql/data_migration_repo/versions/013_protocol_cascade_delete_for_federated_user.py → keystone/common/sql/data_migration_repo/versions/013_migrate_protocol_cascade_delete_for_federated_user.py
View File

0
keystone/common/sql/expand_repo/versions/013_protocol_cascade_delete_for_federated_user.py → keystone/common/sql/expand_repo/versions/013_expand_protocol_cascade_delete_for_federated_user.py
View File

9
keystone/tests/unit/test_sql_banned_operations.py
View File

@ -281,14 +281,7 @@ class TestKeystoneDataMigrations(
# timestamp to datetime and updates the initial value in the contract
# phase. Adding an exception here to pass data migrations banned tests,
# otherwise fails.
4,
# Migration 013 updates a foreign key constraint at the federated_user
# table. It is a composite key pointing to the procotol.id and
# protocol.idp_id columns. Since we can't create a new foreign key
# before dropping the old one and the operations happens in the same
# upgrade phase, adding an exception here to pass the data migration
# banned tests.
13
4
]
def setUp(self):