Bug 1044574 - [RFE] Provide ability to run initial migration stand alone
Summary: [RFE] Provide ability to run initial migration stand alone
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Candlepin
Classification: Community
Component: candlepin
Version: 0.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Michael Stead
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-18 15:27 UTC by Eric Helms
Modified: 2016-07-22 14:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Feature: Reason: Result (if any):
Clone Of:
Environment:
Last Closed: 2016-07-22 14:39:54 UTC
Embargoed:


Attachments (Terms of Use)

Description Eric Helms 2013-12-18 15:27:00 UTC
Currently, the 'cpdb' script combines database creation and the initial migration in one command. A user should be able to handle the database creation through other configuration tool such as puppet and still perform the initial database migration. Currently, the way the database creation is handled requires complicating the Postgresql setup to account for the 'createdb' command in order to get at the call to the initial migration. Thus, it would be highly beneficial to allow the initial migration to be run directly via cpdb.

Comment 1 Michael Stead 2013-12-19 19:05:18 UTC
Pull Request submitted and waiting for review:
https://github.com/candlepin/candlepin/pull/467

Comment 2 Michael Stead 2014-01-03 13:35:19 UTC
Added --schema-only option to cpsetup/cpdb.

When using this option with the create action, skip db creation step and only load the schema.


Available in: candlepin-0.9.2-1+

Comment 3 Mike McCune 2016-03-28 23:11:51 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 4 Barnaby Court 2016-07-22 14:39:54 UTC
Moving to closed per the updated candlepin process for bugs that have been merged or have been taken care of.


Note You need to log in before you can comment on or make changes to this bug.