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

Add community.docker as a requirement for molecule testing #196

Merged
merged 1 commit into from
Jun 1, 2024

Conversation

mcdonnnj
Copy link
Member

🗣 Description

This pull request adds the community.docker collection with a specified minimum version as an explicit requirement for our molecule scenario.

💭 Motivation and context

Without version 3.10.2 of the community.docker collection our molecule testing cannot pass on a fresh install. The latest version of ansible has version 3.10.1 of the community.docker collection and we need a minimum of version 3.10.2 to ensure compatibility with the requests library version 2.32.0 and newer. The next release will not be until next month (June of 2024) and we are still awaiting the merge of ansible-community/molecule-plugins#257 which would ensure 3.10.2 is the minimum version installed for the Docker driver.

🧪 Testing

Automated tests pass.

✅ Pre-approval checklist

  • This PR has an informative and human-readable title.
  • Changes are limited to a single goal - eschew scope creep!
  • All future TODOs are captured in issues, which are referenced
    in code comments.
  • 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.

We explicitly add the `community.docker` collection with a minimum
version as a requirement to the molecule configuration. This will allow
us to ensure that a version of this collection that is compatible with
2.32.0 and newer of the Python requests library is installed.
@mcdonnnj mcdonnnj added bug This issue or pull request addresses broken functionality dependencies Pull requests that update a dependency file labels May 29, 2024
@mcdonnnj mcdonnnj self-assigned this May 29, 2024
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.

Release the mini-kraken!! 🐙 🔥

@mcdonnnj mcdonnnj added the kraken 🐙 This pull request is ready to merge during the next Lineage Kraken release label May 30, 2024
@mcdonnnj mcdonnnj added this pull request to the merge queue Jun 1, 2024
@mcdonnnj mcdonnnj removed this pull request from the merge queue due to a manual request Jun 1, 2024
@mcdonnnj mcdonnnj added this pull request to the merge queue Jun 1, 2024
Merged via the queue into develop with commit 82e9264 Jun 1, 2024
12 checks passed
@mcdonnnj mcdonnnj deleted the bug/specify_collection_version_requirement branch June 1, 2024 22:41
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.

None yet

3 participants