3 Commits

Include renames

Author	SHA1	Message	Date
volker.raschekandCopilot	89e36b89d6	fix(ssh): remove authorized_keys filename for 2.1.0 ... Co-authored-by: Copilot <copilot@github.com>	2026-10-17 22:21:39 +02:00
volker.raschekandCopilot	de280ef620	feat(ssh)!: configure keys with filename and content ... Accept SSH key content directly so callers no longer need role-specific source directories. Update Molecule coverage and documentation. BREAKING CHANGE: private_keys entries must be objects with filename and content instead of file names. authorized_keys entries must provide content alongside filename. Public keys are also written to ~/.ssh. Co-authored-by: Copilot <copilot@github.com>	2026-10-17 21:41:41 +02:00
volker.raschekandCopilot	a343205fd3	test(molecule): cover the role with a molecule scenario ... The role changed a lot and none of it was verified against a real system so far. The scenario starts one container per supported distribution family, applies the role and asserts afterwards that the users and groups exist as declared, that the managed files carry the documented mode, owner and content, that a user without optional settings does not receive any of the optional files and that a user declared as absent is gone again. The idempotence step is the actual reason for the scenario. The deterministic password salt and the btrfs device lookup were changed to stop reporting a change on every run, and only a second converge proves that. A btrfs home is not covered, because a container has no btrfs filesystem to create a subvolume on. The ssh key pair the scenario feeds into the role is generated during create and removed again during destroy, so no private key material ends up in the repository. The generated files are ignored for the case that a destroy never runs. Co-authored-by: Copilot <copilot@github.com>	2026-09-10 09:54:00 +02:00