fix(meta): declare the versions the role actually requires

The role claimed to work with ansible 2.9, but two of its building blocks did not exist back then. The path_join
filter was introduced in ansible-base 2.10 and the btrfs_subvolume module in community.general 6.6.0, which in turn
requires ansible-core 2.11. Running the role on 2.9 therefore failed with an undefined filter instead of a readable
message about an unsupported control node.

The collection is now declared in a requirements.yml, mirroring the layout of the certificate_authority role, and the
lower bound is pinned because an older community.general still resolves but lacks the btrfs module. The linter
workflow installs that file, because ansible-lint cannot resolve the btrfs_subvolume tasks without the collection
being present, which only surfaced in CI where no collections are preinstalled.

Co-authored-by: Copilot <copilot@github.com>

This commit is contained in:

volker.raschek

2026-09-09 21:39:42 +02:00

co-authored by

Copilot

parent 5f757914be

commit 00f465e5e1

4 changed files with 19 additions and 1 deletions

									
										meta/main.yaml
									
		+1
		-1
	
												View File
												
				@@ -9,7 +9,7 @@ galaxy_info:

				  - unix

				  - linux

				  license: "MIT"

				  min_ansible_version: "2.9"

				  min_ansible_version: "2.11"

				  namespace: volker-raschek

				  platforms:

				  - name: ArchLinux