-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
updated pinning to prevent breaking changes #4783
updated pinning to prevent breaking changes #4783
Conversation
/assign @ant31 |
ci check this |
This is a good idea. But can we pin all requirements to a specific version. We should pin Ansible to 2.7 as here, and the rest to the last version gathered with pip install. This would prevent breakage in the future. |
/hold |
totally agreed. I prefer strict pinning. I could update this so that each one is a |
pinned all to a specific version and left it at Ansible 2.7.8 as requested. |
Great ! There is a requirements file in the tests folder too. Can you upgrade that one too. |
added testing pinning information. One note, |
I dont think boto is used anymore. You can try to remove it. |
/lgtm Looks good. This should make things a bit more stable. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: marcstreeter, woopstar The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
* updated ansible pinning to prevent more possibilities of breaking changes * more exact pinning of ansible version * more exact pinning of ansible version and also all the rest * added testing requirements.txt pinning settings * removed boto from testing requirements.txt
* updated ansible pinning to prevent more possibilities of breaking changes * more exact pinning of ansible version * more exact pinning of ansible version and also all the rest * added testing requirements.txt pinning settings * removed boto from testing requirements.txt
* updated ansible pinning to prevent more possibilities of breaking changes * more exact pinning of ansible version * more exact pinning of ansible version and also all the rest * added testing requirements.txt pinning settings * removed boto from testing requirements.txt
* updated ansible pinning to prevent more possibilities of breaking changes * more exact pinning of ansible version * more exact pinning of ansible version and also all the rest * added testing requirements.txt pinning settings * removed boto from testing requirements.txt
What type of PR is this?
kind bug
What this PR does / why we need it:
Currently the pinning scheme allows for more breaking changes than is necessary.
>=2.7.8
could give you2.8.0
or2.7.10
depending on when you ran it. Ansible 2.8.0 breaks deploying Kubespray when 2.7.10 does not. This PR would still allow for the2.7.8
or newer versions of Ansible while not jumping to2.8.*
.Which issue(s) this PR fixes:
Fixes #3985
Special notes for your reviewer:
Does this PR introduce a user-facing change?: