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
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.
Add ability to specify a minor version for
pulpcore_version now defaults to a specific minor release of pulpcore (e.g.: 3.15)
which the installer is going to install.
When the installer is run for the first time, the latest patch release of pulpcore
(e.g.: 3.15.2) is installed. If the installer is run again with the same value of
pulpcore_version, the pulpcore package is not updated. In order to update to the
latest patch release within a minor stream, the user must set
If the user sets the
pulpcore_version to a different minor release of pulpcore
(e.g.: 3.16), the installer will attempt to upgrade pulpcore to the latest patch
release (e.g.: 3.16.1) for that minor release of pulpcore.
If the user sets the
pulpcore_version to a specific patch release, the installer
will attempt to install that specific release of pulpcore.
If the installed plugins are not compatible with the requested release of pulpcore, the installer will not make any changes.
version of a plugin can now also be specified as a minor release (e.g.: 1.8) or
a specific patch release (e.g.: 1.8.2). When the a minor release is specified and it
is the same as the installed version of the plugin, the
upgrade parameter for that
plugin must be set to
true in order for the plugin to be updated to the latest
The internal variable
__pulp_version was renamed to
The release-static test scenario for molecule was also updated to test this feature.
#1 Updated by firstname.lastname@example.org 5 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
#4 Updated by email@example.com 18 days ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset ansible-pulp|aaa52ba2aa5db0186da579a76044509ac4b4cc95.
Please register to edit this issue