Skip to content
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

Pin the version of the ansible package #309

Merged
merged 1 commit into from
Mar 7, 2024
Merged

Conversation

mcdonnnj
Copy link
Member

@mcdonnnj mcdonnnj commented Mar 6, 2024

🗣 Description

This pull request adds a version pin constraint for the ansible package in the requirements. This pin constraint matches the one in cisagov/skeleton-ansible-role#173.

💭 Motivation and context

We should be mirroring the version of ansible used by cisagov/skeleton-ansible-role and its descendants to ensure consistency.

🧪 Testing

This pull request needs #295 to pass tests. You can see everything working as expected in this run on a branch that combines both branches.

✅ Pre-approval checklist

  • This PR has an informative and human-readable title.
  • Changes are limited to a single goal - eschew scope creep!
  • All relevant type-of-change labels have been added.
  • I have read the CONTRIBUTING document.
  • These code changes follow cisagov code standards.
  • All new and existing tests pass.

@mcdonnnj mcdonnnj added bug This issue or pull request addresses broken functionality dependencies Pull requests that update a dependency file labels Mar 6, 2024
@mcdonnnj mcdonnnj self-assigned this Mar 6, 2024
@jsf9k jsf9k requested a review from a team March 6, 2024 18:59
@jsf9k
Copy link
Member

jsf9k commented Mar 6, 2024

I suggest that the bug tag is a bit strong for this PR. Improvement would be a better fit IMHO.

@mcdonnnj
Copy link
Member Author

mcdonnnj commented Mar 6, 2024

I suggest that the bug tag is a bit strong for this PR. Improvement would be a better fit IMHO.

I'm calling it a bug because the dependency should have been pinned alongside cisagov/skeleton-ansible-role@839fe4b almost four years ago. We're just lucky the build process hasn't allowed a stale version of Ansible to be used or we would have noticed things breaking unexpectedly for some image configurations.

Copy link
Member

@dav3r dav3r left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 👍

@mcdonnnj mcdonnnj added the kraken 🐙 This pull request is ready to merge during the next Lineage Kraken release label Mar 6, 2024
We should be pinning the version of Ansible we use in our Packer
projects to mirror the version used in our Ansible role projects.

Co-authored-by: Shane Frasier <[email protected]>
@mcdonnnj mcdonnnj force-pushed the bug/pin_ansible_version branch from f2303b9 to dd67feb Compare March 7, 2024 13:23
@mcdonnnj mcdonnnj added this pull request to the merge queue Mar 7, 2024
Merged via the queue into develop with commit 0820605 Mar 7, 2024
9 checks passed
@mcdonnnj mcdonnnj deleted the bug/pin_ansible_version branch March 7, 2024 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue or pull request addresses broken functionality dependencies Pull requests that update a dependency file kraken 🐙 This pull request is ready to merge during the next Lineage Kraken release
Projects
Development

Successfully merging this pull request may close these issues.

4 participants