Project

Profile

Help

Story #8847

Story #8846: As a pulp_installer user, I do not need to use the latest micro release to install the latest micro release of pulpcore

As a pulp_installer user, I can specify variables for the minor release branch of pulpcore/plugins

Added by mdepaulo@redhat.com about 2 months ago. Updated about 2 months ago.

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

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

The tentative design is the following variables:

pulpcore_branch: defaults to the same minor release branch as the installer, and we do not want users to change this

pulpcore_update: boolean, defaults to false for idempotency, whether to update to the latest micro release on the minor release branch

pulp_install_plugins.plugin-name.branch: no default value, users are encouraged to provide it in the format like "3.14"

pulp_install_plugins.plugin-name.update: boolean, defaults to false for idempotency, whether to update to the latest micro release on the minor release branch

It also means that when say a user runs pulp_installer 3.15 against pulpcore 3.14, the "upgrade" must happen. This is the current logic, but it needs to be updated for the new logic above.

docs/customizing.md will need particular updates.

History

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

  • Subject changed from As a pulp_installer user, I can specify variables for the minor release branch of pulpcore/plugins, and whether to update within that branch to As a pulp_installer user, I can specify variables for the minor release branch of pulpcore/plugins

#2 Updated by mdepaulo@redhat.com about 2 months ago

  • Description updated (diff)

Please register to edit this issue

Also available in: Atom PDF