Felix Fontein

> @felixfontein thanks for clarification, now should be much clear. > If I understood, correct if I'm wrong, your use case is to reject element in a list that match...

This is very likely a Ansible usage problem. Modules do not run in the same Python context that ansible-core runs in. You need to explicitly tell Ansible where to run...

The shebang is definitely unrelated. You need to configure ansible-core to run modules in the venv. How exactly that works I don't know (never tried it).

Ref: https://github.com/ansible/ansible/issues/85037

@chriscarpenter12 why not simply put them in `.sops.yaml` and store that in the root of the repo that should contain the SOPS encrypted files?

Here's a small example: ```.yaml creation_rules: - age: >- age1yt3tfqlfrwdwx0z0ynwplcr6qxcxfaqycuprpmy89nr83ltx74tqdpszlw, age129h70qwx39k7h5x6l9hg566nwm53527zvamre8vep9e3plsm44uqgy8gla, age129h70qwx39k7h5x6l9hg56qxcxfaqycuprpmy89nr83ltx74tqdpszlw ``` (A more complex one: https://github.com/getsops/sops?tab=readme-ov-file#using-sopsyaml-conf-to-select-kms-pgp-and-age-for-new-files)

> Is there a particular reason why this isn't supported? It's simply because it is not implemented that way, and hasn't changed yet. (There's a PR (#849), but it needs...

Since there is no fixed file pattern of how SOPS encrypted files are named, this is kind of hard to implement. It's generally best if you create a shell script...

docker_container does not know about Docker Swarm and that very likely won't change, so if the network isn't present on the Docker daemon you run it against, it will complain...

It's basically a limitation of Docker. `docker network ls` will only find the network if it's already used by a container for the local daemon (or something like that, I...