Remove SQL Schema Downgrades

Remove SQL Schema Downgrades

Trove still has the downgrade method on its migration files. Following the cross-project spec https://review.openstack.org/#/c/152337/ we are supposed to remove the downgrade to avoid data inconsistency, lack of integrity, etc. This approach was already done in many projects like Keystone, Magnum, Nova and others [2][3][4][5].

Launchpad Blueprint: https://blueprints.launchpad.net/trove/+spec/remove-sql-schema-downgrades

Problem Description

Downgrades are not the best idea when thinking about data integrity. A cross project spec was proposed to start removing downgrades and it was already done in many projects. We need to delete downgrade from migration files.

Proposed Change

Remove downgrades from migration files and remove the command from trove-manage.

Configuration

None

Database

None

Public API

None

Public API Security

None

Python API

None

CLI (python-troveclient)

None

Internal API

None

Guest Agent

None

Alternatives

None

Dashboard Impact (UX)

TBD (section added after approval)

Implementation

Assignee(s)

<tellesmvn>

Milestones

Mitaka-1

Work Items

This work is basically removing downgrades, removing the command from trove-manage and update the tests.

Upgrade Implications

None

Dependencies

None

Testing

We need to update the tests so they will not fail when trying to downgrade.

Documentation Impact

None

Appendix

None

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.

trove-specs 0.0.1.dev177