Any content type which doesn't have on_demand support should not be checked on re-runs for RemoteArtifact needs
We look at all the content on every re-run (in the future it will be only affected content) to create RemoteArtifatcs if they are missing.
There is a configuration on the plugin migrator
lazy_types which helps to identify which content might need to have RemoteArtifacts. Any non-lazy types should be skipped if content is migrated.
- Status changed from NEW to POST
- Assignee set to ttereshc
- Sprint set to Sprint 71
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp:pulp-2to3-migration|42eb40279b797b6cfc1af6ea3e21498fe098acc9.
Please register to edit this issue