empty repositories should still be migrated if they are specified in the migration plan
Currently if i have an empty repository in my migration plan, it is not migrated. We need to ensure that all yum repos are migrated, even if they are empty. From IRC:
ipanova: well a user has some repository in katello, maybe they just created it, maybe its been around for a while
but for whatever reason they haven't done anything with it yet
some client might be subscribed to it
its not necessarily an intentional use case
but a possibility
and all repos, empty or not, need to be available at the same path in pulp3 as they were in pulp2
some yum client could be configured to use it and start erroring if it starts getting 404s
#5 Updated by dalley over 1 year ago
- Status changed from ASSIGNED to POST
#6 Updated by dalley over 1 year ago
Closed the first PR because the commit depends on one from another PR, and it's simpler this way.
#9 Updated by dalley over 1 year ago
- Status changed from POST to MODIFIED
Applied in changeset pulp:pulp-2to3-migration|648bcfc2613c64913f4fd770e96418f868ce319f.
#10 Updated by dalley over 1 year ago
Applied in changeset pulp-2to3-migration|648bcfc2613c64913f4fd770e96418f868ce319f.
#11 Updated by dalley over 1 year ago
Applied in changeset pulp:pulp-2to3-migrate|648bcfc2613c64913f4fd770e96418f868ce319f.
Please register to edit this issue