Project

Profile

Help

Story #7815

closed

As a plugin writer, pulpcore ensures that a job working directory is set/removed properly

Added by ttereshc over 3 years ago. Updated about 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Sprint 90
Quarter:

Description

Motivation

At the moment, it's plugin's responsibility to be sure that any temporary files it's working with are stored in the directory dedicated to a running job. It's done by using the content manager WorkingDirectory.
The context manager doesn't support nesting which causes a usability problem.
Plugin writer needs to carefully create and recreate the working directory every time it deals with files to avoid nesting (e.g. stages API uses WorkingDirectory so some nesting can come from the using of pulpcore code).

Suggestion

  • let tasking management in pulpcore take care of managing the working directory for every job (even if it doesn't need it)
  • raise DeprecationWarning for the context manager WorkingDirectory
  • make the context manager WorkingDirectory no-op since pulpcore sets the directory for any job
  • file a task to remove the deprecation and the context manager on Y+1 version of pulpcore

Related issues

Blocks File Support - Story #7469: as a Pulp File user, I can have my repository auto published and distributedCLOSED - CURRENTRELEASEdalley

Actions
Blocks RPM Support - Story #6353: As a user, I can mirror RPM repository content and metadataCLOSED - CURRENTRELEASEdalley

Actions

Also available in: Atom PDF