Project

Profile

Help

Story #3777

As a plugin writer, I am instructed how to handle migrations

Added by amacdona@redhat.com about 2 years ago. Updated 15 days ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation, Easy Fix, Plugin Template
Sprint:

Description

For development, we recommend keeping the migrations out of the git repository by adding them to the .gitignore.

When the model layer has stabilized, the migrations should be committed (and removed from the .gitignore).

History

#1 Updated by amacdona@redhat.com about 2 years ago

  • Sprint Candidate changed from Yes to No

#2 Updated by bmbouter over 1 year ago

  • Tags deleted (Pulp 3)

#3 Updated by bmbouter over 1 year ago

  • Tags Plugin Template added

#4 Updated by bmbouter over 1 year ago

  • Project changed from 27 to Pulp

The plugin template Redmine project is being consolidated into the Pulp Redmine project so all issues are being moved over.

#5 Updated by Starkgene 15 days ago

Are there dependencies on Django for Pulp 3? I've just found integration gaps doc here:

https://docs.google.com/document/d/1eFM4H9BteA_nTDbUkRJgEiqSttXfAtB9-51a_OuwVJw/edit#heading=h.w5qlb95lzl4k

___________________________________________ Migration scripts for a plugin writer https://thetermpapers.org

Please register to edit this issue

Also available in: Atom PDF