kevinveenbirkenbachandClaude Opus 5 7e1d336869 fix(vault): keep ansible off the CI runner host's import path ...

e41be38cb replaced the ansible-vault subprocess with in-process VaultLib and imported ansible at module level. That pulled it into the chain cli.administration.deploy.development -> credentials_generator -> utils/manager/inventory.py -> utils/handler/vault.py, which the CI runner host resolves without ansible installed. Before that commit the module imported only subprocess and yaml, so the import cost nothing.

test_ci_host_dependencies names both remedies: declare the dependency in [project.dependencies], or make the import lazy. Lazy is right here because ansible serves one branch of this module and the declaration would be paid for on every CI job. _vault is already a cached_property, so the import runs once per handler instance and only when something actually encrypts.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-08 22:28:47 +02:00

..

__init__.py

Rename module_utils package to utils

2026-03-21 02:05:39 +01:00

vault.py

fix(vault): keep ansible off the CI runner host's import path

2026-09-08 22:28:47 +02:00

yaml.py

style: delete every comment the comments-valid policy rejects

2026-08-18 03:22:02 +02:00