Project

Profile

Help

Story #8847

Updated by mdepaulo@redhat.com 6 months ago

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.

Back