Task #2893: Add Publication and Distribution models. - Pulp

Agile board
Agile charts

Agile boards

Pulp 2 QE Agile Board
Pulp 2 QE Agile Board - Priority View
Pulp 3 QE Agile Board
Pulp 3 RPM Tests Agile Board
Sprint 112 Agile Board

Custom queries

[All Projects] All Test Trackers
2.21.4 - Next Bugfix Release
2.21.4 MODIFIED
2.21.5
3.14.3
CI/CD
Easy Fix
FIPS open
Functional Tests
Galaxy NG
Groomed
Installer - Triage
Installer Items
Issues for Triage
Katello Integration
Next Docs Day
Operator issues
POST/ASSIGNED - no Sprint - Pulp2
POST/ASSIGNED - no Sprint - Pulp3
Prioritized Bugs
Pulp 3 Docs issues
Pulp2 issues available for next release
Pulpcore
SELinux related
Sprint 111
Sprint 112
Sprint Candidates (also groomed)
Un-Triaged Bugs
Verification Required

Actions

Send by e-mail Copy link

Task #2893

closed

Task #2868: Platform support for publishing.

Add Publication and Distribution models.

Added by jortel@redhat.com almost 7 years ago. Updated over 4 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

High

Assignee:

jortel@redhat.com

Category:

Sprint/Milestone:

3.0.0

Start date:

Due date:

% Done:

Estimated time:

Platform Release:

Groomed:

Yes

Sprint Candidate:

Yes

Tags:

Sprint:

Sprint 25

Quarter:

Description

Add publication and distribution models as defined in #2868

The Publication, PublishedArtifact and PublishedMetadata models should be imported into the plugin API to support publishing.

Related issues

Blocked by Pulp - Story #2872: As an authenticated user, I can create a Content unit from one or more artifacts

CLOSED - CURRENTRELEASE

dkliban@redhat.com

Actions

Blocks Pulp - Task #2916: Add Distribution serializer and viewset.

CLOSED - CURRENTRELEASE

amacdona@redhat.com

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by mhrivnak almost 7 years ago

To confirm, we are deliberately not creating serializers and viewsets for this right now, correct? That would be valuable to capture in the description with a quick explanation for why.

Actions

Copy link

Updated by jortel@redhat.com almost 7 years ago

mhrivnak wrote:

To confirm, we are deliberately not creating serializers and viewsets for this right now, correct? That would be valuable to capture in the description with a quick explanation for why.

Correct. I don't think we have a use case for exposing publications through the REST API. Publications no longer referenced by any Distribution can be cleaned up by something internal to the platform.

Although, we may need to expose Publications though REST API for Distribution promotion work flows.

This probably needs further discussion.

Actions

Copy link