Public bug reported:
To ensure that each of the 3 new migration repositories contain the same
number of steps, we should introduce a test to catch developers
attempting to introduce a new step to any one of the new repos, without
introducing no-op steps to all of them.
Upon failure, the test should explain to developers that they need to
add no-op migrations to the other repositories, and the motivation for
doing so (e.g. making it easy for us to prevent deployers from breaking
their databases).
** Affects: keystone
Importance: Low
Status: Triaged
** Tags: test-improvement upgrades
** Summary changed:
- Test that expand, migrate, contract migration repos have the same number of
migrations
+ Test that expand, migrate, contract repos have the same number of steps
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1615020
Title:
Test that expand, migrate, contract repos have the same number of
steps
Status in OpenStack Identity (keystone):
Triaged
Bug description:
To ensure that each of the 3 new migration repositories contain the
same number of steps, we should introduce a test to catch developers
attempting to introduce a new step to any one of the new repos,
without introducing no-op steps to all of them.
Upon failure, the test should explain to developers that they need to
add no-op migrations to the other repositories, and the motivation for
doing so (e.g. making it easy for us to prevent deployers from
breaking their databases).
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1615020/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
