Project

Profile

Help

Task #2702

closed

Install Plugins into Pulp 3 development env

Added by semyers almost 7 years ago. Updated almost 5 years ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Dev Environment, Pulp 2
Sprint:
Quarter:

Description

I recently added a task to the 3.0 dev playbook to install pulp_file into the platform virtualenv on install. As seen in the comments on that block, this is a bit of a placeholder just to get pulp_file into platform so that you can do fun things with the platform API.

We need to come up with a mechanism that ansible can easily use for installing plugins for Pulp 3. Maybe this is continuing to rely on each plugin providing a "pulp-dev.py" executable, maybe we require all plugins to be installable with "python setup.py develop"; whatever we go with would ideally be consistent across plugins.

In addition to installing plugins into the platform virtualenv for use together, we should also make sure to install plugins into their own virtualenvs, allowing them to be worked on in isolation from other plugins.

Also available in: Atom PDF