Mark certain configuration options as deprecated

Bug #1375428 reported by Peter Stachowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Confirmed
Low
Unassigned

Bug Description

A number of configuration options have been moved to a per-datastore implementation. As such, they should be marked as 'deprecated' in the DEFAULT section of the configuration file.

This attempts to do a cleanup of the volume and backup options and to prepare for a final cleanup (of the newly deprecated options) in a future release.

Changed in trove:
assignee: nobody → Peter Stachowski (peterstac)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

Fix proposed to branch: master
Review: https://review.openstack.org/124846

Changed in trove:
status: New → In Progress
Amrith Kumar (amrith)
Changed in trove:
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on trove (master)

Change abandoned by Peter Stachowski (<email address hidden>) on branch: master
Review: https://review.openstack.org/124846

Revision history for this message
Amrith Kumar (amrith) wrote :

Peter, any updates on this?

Revision history for this message
Peter Stachowski (peterstac) wrote :

Nobody like the fix, so I abandoned it - I'll take my name off of the bug ;)

Changed in trove:
assignee: Peter Stachowski (peterstac) → nobody
status: In Progress → New
Amrith Kumar (amrith)
Changed in trove:
status: New → Incomplete
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.