Replace sequence-update `post_migrate` hook with a migration

Open
#2,246 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
database

Research direction

Start by reviewing pull request 2235 and locating the sequence-update post_migrate hook it introduced. Compare it with the project's existing migration patterns; done means the hook is replaced by a migration and the ALTER runs only once on new installs and upgrades.

Written by the indexing model from the issue text.

Description

Task

https://github.com/pulp/pulp_container/pull/2235 uses a post_migrate hook to fix its issue in order to make the fix backport-able. Going forward, let's replace that with an actual migration, in order to make it clear what's going on, and to execute the ALTER only once on new installs/upgrades.

Dominant language
Python
Stars
31
Forks
56
Avg merge
2d 22h
Merged PRs (30d)
22

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pulp/pulp_container

All issues in pulp/pulp_container

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.