Issue #8626
closed
Migrate relationship between repo and importer to Pulp 3
Description
The relationship between Pulp 3 remotes and repositories is currently stored in the Pulp2Repositories table, but this is only temporary and will eventually be deleted from installations. Pulp 3 has an equivalent relationship already, the "remote" field on the Repository model, and it would be ideal if we could go ahead and migrate that information.
Updated by quba42 almost 3 years ago
Note: As I remarked on the PR, using the remote field on the Repository model only works for plugins that have added the relevant remote types to the REMOTE_TYPES list (otherwise an error is thrown).
For pulp_deb this is not the case for any released version (though it has been merged to main: https://github.com/pulp/pulp_deb/pull/261). I don't know about other plugins.
Added by dalley almost 3 years ago
Added by dalley almost 3 years ago
Revision 3462b2c2 | View on GitHub
Migrate relationship between repo and importer to Pulp 3
Populate the "remote" field on the Pulp 3 repository model with the information stored in the Pulp2Repositories table, so that it can survive post-migration.
Added by dalley almost 3 years ago
Revision 3462b2c2 | View on GitHub
Migrate relationship between repo and importer to Pulp 3
Populate the "remote" field on the Pulp 3 repository model with the information stored in the Pulp2Repositories table, so that it can survive post-migration.
Updated by dalley almost 3 years ago
- Status changed from ASSIGNED to MODIFIED
Applied in changeset pulp:pulp-2to3-migration|3462b2c268f486f1b600e38dad0c0e0deadf2110.
Updated by pulpbot almost 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Migrate relationship between repo and importer to Pulp 3
Populate the "remote" field on the Pulp 3 repository model with the information stored in the Pulp2Repositories table, so that it can survive post-migration.
closes: #8626 https://pulp.plan.io/issues/8626