Story #1884: As a user, I can lazily sync python packages - Python Support - Pulp

Actions

Send by e-mail Copy link

Story #1884

closed

Pulp - Story #3693: Lazy for Pulp3

As a user, I can lazily sync python packages

Added by amacdona@redhat.com over 8 years ago. Updated almost 4 years ago.

Status:

MODIFIED

Priority:

Normal

Assignee:

CodeHeeler

Sprint/Milestone:

3.0 GA

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

3.0.0

Target Release - Python:

Groomed:

Yes

Sprint Candidate:

Tags:

Sprint:

Sprint 51

Quarter:

Description

With the previous work done in for python packages, it is now possible to create objects using only the metadata provided by the json API of PyPI. This metadata is also now provided by pulp publish.

Completion of this story should allow the user to set the download policy to on_demand and background.

Related issues

Actions

Copy link

Updated by amacdona@redhat.com over 8 years ago

Blocked by Story #1882: Rebuild model to support all package types added

Actions

Copy link

Updated by amacdona@redhat.com over 8 years ago

Blocked by Story #1883: As a user, I can sync and publish all package types added

Actions

Copy link

Updated by amacdona@redhat.com over 8 years ago

Blocked by Issue #1183: As a developer, I can close this ticket as a duplicate of 1884 :) added

Actions

Copy link

Updated by mhrivnak over 8 years ago

I think this should be a story instead of an issue.

The description dives right into how to do this, but skips over what the goal is. :) "Lazy integration" is perhaps obvious to some, but it's helpful to have a more full description. Start with the desired behavior: we want the ability to set the download policy to on_demand or background. Describe the workflow of specifying that setting, accessing content, having it retrieved on-demand, etc. What will QE do to verify this?

The checklist is a good place for implementation details, including: add catalog entries during sync, document new importer settings, make new importer settings available in pulp-admin, add release notes, etc.

The "downloaded" boolean is already on FileContentUnit in platform, so you'll get that for free.

I'm not sure about the idea of updating the unit in the DB after download. Pulp's job is a LOT easier when units are immutable. Do we really need to update it for some reason?

Actions

Copy link

Updated by dkliban@redhat.com over 8 years ago

Triaged changed from No to Yes

Actions

Copy link

Updated by dkliban@redhat.com over 8 years ago

Triaged changed from Yes to No

Actions

Copy link

Updated by amacdona@redhat.com over 8 years ago

Tracker changed from Issue to Story
Subject changed from Lazy integration to As a user, I can lazily sync python packages
Groomed set to No
Sprint Candidate set to No