R. P. Taylor

> My GUESS is that the when conditions are added to the containerd handlers when import_role That is exactly how import_* works. (See also https://github.com/kubernetes-sigs/kubespray/issues/9279 , https://serverfault.com/questions/875247/whats-the-difference-between-include-tasks-and-import-tasks ) > since...

It's also slightly odd that the restart containerd handler is a no-op that just calls another handler: https://github.com/kubernetes-sigs/kubespray/blob/master/roles/container-engine/containerd/handlers/main.yml Probably the other handlers should `listen` instead. It should work though but...

"the location where it is inserted doesn't affect when the handlers are added" https://github.com/ansible/ansible/issues/78871#issuecomment-1258170633

@lxbsz do you know where the most recent error is coming from? Thanks for taking a look if you can!

Looks like it is approved, does that mean it can be merged? Thanks for working on the fix!

Looks like something related was implemented in https://github.com/theskumar/python-dotenv/pull/388 Instead of the `raise_exception=True` parameter it looks like users will have to check the boolean return code.

Also there isn't a warning if Verbose is on and the file doesn't exist: ``` import dotenv a=dotenv.load_dotenv('no.env', verbose=True) print(a) False ```

I found an Ara helm chart here: https://artifacthub.io/packages/helm/lib42/ara Haven't tried it yet.

Using versioned image tags is widely regarded as a good practice for reproducible and declarative deployments. This is especially helpful for Helm chart deployments, where the image tag and Helm...

So is it safe to say that dcache can handle a CA update without needing to restart gplazma anymore, in >= v7.2 at least?