Story #6794: As a pulp_installer user, I can specify a repo full of RPMs to install Pulp from - Pulp

Actions

Send by e-mail Copy link

Story #6794

closed

Story #6793: [Epic] As a pulp_installer user, I can install Pulp from RPMs

As a pulp_installer user, I can specify a repo full of RPMs to install Pulp from

Added by mdepaulo@redhat.com almost 4 years ago. Updated almost 4 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

Category:

Installer - Moved to GitHub issues

Sprint/Milestone:

3.5.0

Start date:

Due date:

% Done:

Estimated time:

Platform Release:

Groomed:

Sprint Candidate:

Tags:

Sprint:

Quarter:

Description

The installer should add the repo to the managed system, but should not attempt any default value. It is therefore the responsbility of the user, and the repo's maintainers, to specify a repo with the RPMs. And for the set of RPMs to be compatible with each other.

Added by Mike DePaulo almost 4 years ago

Revision 184f1235 | View on GitHub

As a pulp_installer user, I can install Pulp from RPMs

Heavily adapted from "allow installing pulp from packages"

https://github.com/pulp/pulp_installer/pull/188

Includes:

Dropping the fixed repo from the old PR.
Add var pulp_pkg_repo (currently only yum/dnf)
Finish cleaning up pulp_webserver_static_dir
Many new variables, but still using the overall pulp_install_plugins.
Testing upgrades with new images on quay (can't truly test until RPM updates are issued)
Cron/branch CI: Adding py38 testing
PR CI: Move upgrade testing from py37 to py38, and testing from RPMs on py37.
Deduplicating the tasks for checking plugins for nginx/apache snippets.
Using pulp_django_admin_paths list var because RPMs often use different names for django-admin.
Note: Rest of tasks should be package manager independent.
pulp_upgraded_manually variable in case users ran yum update
package only variables in seperate section of the pulp README.md.

fixes: #6793