Project

Profile

Help

Story #6824

closed

Handle schema conversion when s3 is set as a storage backend

Added by ipanova@redhat.com over 2 years ago. Updated about 2 years 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)

Actions #1

Updated by ipanova@redhat.com over 2 years ago

  • Sprint/Milestone set to 2.0.0
Actions #2

Updated by mdellweg about 2 years ago

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

Updated by pulpbot about 2 years ago

  • Status changed from ASSIGNED to POST

Added by mdellweg about 2 years ago

Revision 41ef636d

Redirect tag lookup to content app

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

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

Added by mdellweg about 2 years ago

Revision 41ef636d

Redirect tag lookup to content app

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

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

Actions #4

Updated by mdellweg about 2 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #6

Updated by mdellweg about 2 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF