Eugene Davis

@rezo552 I had the same error, and found I had to login once with the built-in authentication (with redirects on the proxy disabled) and then re-enable the Home Assistant configuration...

Hi @manolomartinez, I got a bit caught up in making the name for the new functionality make sense. How about I make sure that the tagging section checks for `file_to_tag`...

The use case here is allowing configuration of filenames that the built-in download-handler uses when it actually downloads an episode. This allows customization of filenames without using an external download...

> "Do one thing well" and all that. I would suggest that here that means either removing the download functionality entirely or updating it to cleanly handle feeds with the...

> Thanks for the explanation about your use case, Eugene. I think I agree that the situation right now is kind of unstable; we have a vanilla downloader, but for...

Seeing the same issue with Authentik. Looks to be due to https://github.com/firefly-iii/firefly-iii/issues/6619 A downgrade to 5.7.14 and I can get past this point but instead get a JSON parse error...

If I find time (which might be a while) I can try to add this, but since I see at least a couple of ways to approach it I didn't...

Hi @marioasabella, you can definitely monitoring recursively within a mount point - see [Config examples](https://github.com/tomtom-international/vault-assessment-prometheus-exporter/blob/main/docs/CONFIGURATION_EXAMPLES.md#complete-complex-configuration-for-expiration-monitoring) and [Secret Configuration](https://github.com/tomtom-international/vault-assessment-prometheus-exporter/blob/main/vault_monitor/expiration_monitor/README.md#secret-configuration) Regarding monitoring all the mount paths, aside from the extra logic required...

Had to rebase due to missing signatures

Is there already an open feature request comments in the cookie cutter template? Maybe it is something we could put a PR in for?