Actions
Story #6824
closedHandle schema conversion when s3 is set as a storage backend
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 76
Quarter:
Description
Handle schema conversion when s3 is set as a storage backend and content was synced with immediate_policy
NB. Figure out how to distinguish whether the content was mirrored or pushed into the repo( introduce new repo type for docker push)
Updated by mdellweg about 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to mdellweg
- Sprint set to Sprint 76
Updated by pulpbot about 4 years ago
- Status changed from ASSIGNED to POST
Added by mdellweg about 4 years ago
Added by mdellweg about 4 years ago
Revision 41ef636d | View on GitHub
Redirect tag lookup to content app
Also repaired schema conversion to work with s3 (django-storage).
Updated by mdellweg about 4 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset 41ef636db327b6d89020f685fd353c65c8ee71a3.
Updated by pulpbot about 4 years ago
Updated by mdellweg almost 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Redirect tag lookup to content app
Also repaired schema conversion to work with s3 (django-storage).
fixes #6824 https://pulp.plan.io/issues/6824