Project

Profile

Help

Story #6824

Handle schema conversion when s3 is set as a storage backend

Added by ipanova@redhat.com over 1 year ago. Updated about 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
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)

Associated revisions

Revision 41ef636d View on GitHub
Added by mdellweg over 1 year ago

Redirect tag lookup to content app

Also repaired schema conversion to work with s3 (django-storage).

fixes #6824 https://pulp.plan.io/issues/6824

Revision 41ef636d View on GitHub
Added by mdellweg over 1 year ago

Redirect tag lookup to content app

Also repaired schema conversion to work with s3 (django-storage).

fixes #6824 https://pulp.plan.io/issues/6824

History

#1 Updated by ipanova@redhat.com over 1 year ago

  • Sprint/Milestone set to 2.0.0

#2 Updated by mdellweg over 1 year ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to mdellweg
  • Sprint set to Sprint 76

#3 Updated by pulpbot over 1 year ago

  • Status changed from ASSIGNED to POST

#4 Updated by mdellweg over 1 year ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#6 Updated by mdellweg about 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF