From dd67feb6c5a01b8b9d6b4605a48bb898b4fa91ec Mon Sep 17 00:00:00 2001 From: Nicholas McDonnell <50747025+mcdonnnj@users.noreply.github.com> Date: Wed, 6 Mar 2024 13:17:07 -0500 Subject: [PATCH] Pin the version of the ansible package 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 --- requirements.txt | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/requirements.txt b/requirements.txt index 79ae56ce..c0b40d80 100644 --- a/requirements.txt +++ b/requirements.txt @@ -1,4 +1,18 @@ -ansible +# With the release of version 2.10, Ansible finally correctly +# identifies Kali Linux as being the Kali distribution of the Debian +# OS family. This simplifies a lot of things for roles that support +# Kali Linux, so it makes sense to force the installation of Ansible +# 2.10 or newer. +# +# We need at least version 6 to correctly identify Amazon Linux 2023 +# as using the dnf package manager, and version 8 is currently the +# oldest supported version. +# +# We have tested against version 9. We want to avoid automatically +# jumping to another major version without testing, since there are +# often breaking changes across major versions. This is the reason +# for the upper bound. +ansible>=8,<10 boto3 docopt semver