New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package: Honor specified versions #495
Conversation
|
Attached issue: https://pulp.plan.io/issues/7841 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, but update the package mode docs also:
https://github.com/pulp/pulp_installer/tree/master/roles/pulp_common#role-variables-if-installing-from-rpms
7b052c6
to
3b442bd
Compare
|
@mikedep333 Updated. Please let me know if that matches what you expected |
|
@mikedep333 @mdellweg @fao89 The failures in the CI are not code failures, but the fact that master point to How would you like this to be handled ? |
Hmm, so I suggest we separate it into 2 variables:
For RPM installs, if |
7696a8c
to
a7c406f
Compare
|
@mikedep333 @fao89 re-ready for review, with passing tests this time :) |
a7c406f
to
9c0062a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this needs a rebase.
roles/pulp_common/defaults/main.yml
Outdated
| # pulp_version. | ||
| # Ignored if pulp_source_dir is set | ||
| pulp_version: "3.8.1" | ||
| __pulp_version: '{{ pulp_version | default("3.8.1") }}' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe, this should move to vars.
Also if i read it correctly, it is only used for pip installs. It should maybe be called __pulp_common_pulpcore_pip_version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree on moving it to the vars/main.yml file.
For the rename, I tend to lean toward keeping __pulp_version. It is generic and accurate enough that this value can be leveraged for other purposed that is not pip related specifically.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is only used for pip installations. And for anything else i guess one should use pulp_version.
Ideally we didn't even default_pin the python version in the installer and just install latest from pypi or the specified version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mikedep333 @fao89 @dkliban what are your thoughts on that one ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Spredzy : @mdellweg and I discussed this last meeting. There were multiple problems that pinning the version solved. This one in particular seemed to be the most tricky to solve.
- Handling the case where a user may run an outdated installer to install the current version of Pulp, and thus either the install failing or pulp failing at runtime because of it.
https://pulp.plan.io/issues/5890
I am open to alternate approaches, but we should review them based on the discussions in that issue and the feedback in the initial design PR (that was centered around branches).
roles/pulp_common/README.md
Outdated
| Role Variables for advanced usage | ||
| --------------------------------- | ||
|
|
||
| * `pulp_version`: Specify a specific version of pulpcore one would like to install or upgrade to. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should call it pulpcore_version.
We should be able to rename it today, since it was never advertised before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would be a backward incompatible change. pulp_version is already present before this PR and hence user might be leveraging it. While I agree it would make more sense, (maybe going to a deprecation period) - I don't think this should happen as part of this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing things that are not part of an official interface is the privilege of upstream.
This variable was even described as "intentionally not advertised".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mikedep333 @fao89 @dkliban what are your thoughts on that one ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I am in favor of renaming it to pulpcore_version.
9c0062a
to
3f2c1f8
Compare
3f2c1f8
to
4298426
Compare
4298426
to
5f32072
Compare
fixes: #7841
5f32072
to
6804359
Compare
fixes: #7841