Project

Profile

Help

Story #7469

as a Pulp File user, I can have my repository auto published and distributed

Added by dkliban@redhat.com about 2 months ago. Updated 1 day ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Q1-2021

Description

As a CLI user or a Web UI user, I would like to be able to sync/publish/distribute a repository with a single operation.

In order to support such a feature, the user needs to be able to associate a File Distribution with a File Repository. This would be a new attribute of a File Repository.

The repository sync API needs to accept an additional parameter called 'auto_distribute'. When such a parameter is supplied, the sync task needs to create a new repository version, a new publication, and update the File DIstribution with the latest repository version.

History

#1 Updated by dkliban@redhat.com about 2 months ago

  • Project changed from Pulp to File Support

#2 Updated by bmbouter about 1 month ago

One question I have is about whether the sync and publish will occur as one task or two. From a user, usability perspective having a single task to monitor I think would be easier. Functionally speaking both tasks require a lock on the repository right? If so, then having them run as one task is equally efficient to having them run as two.

#3 Updated by dkliban@redhat.com about 1 month ago

This will run in a single task. The user will monitor a single task. You are correct that both sync and publish lock on a repository.

#4 Updated by daviddavis about 1 month ago

Yea, I think it has to be a single task for the Web UI. Otherwise, if I kick off a sync-and-publish task and then close my browser, then the publish never happens.

#5 Updated by daviddavis 1 day ago

  • Quarter set to Q1-2021

#6 Updated by daviddavis 1 day ago

Updated quarter based on last 3-month planning meeting.

#7 Updated by dkliban@redhat.com 1 day ago

Users would like to be able to specify at sync time whether the spawned task should only sync, sync and publish, or sync, publish, and distribute.

Please register to edit this issue

Also available in: Atom PDF