Arne Groskurth

Any update on this?

A reason to support this might be to allow incremental development/prototyping with monolog - the argument about the performance impact is very valid but that is something that, depending on...

> thinking not sure why the End-to-End Tests / e2e-Tests: e2e_check_requirements build is failing. The build is passing on master so it should be related, but `tee` should pick up...

Yes, that obviously covers the general case. But I think there could also be *some* default logging solution that can be used at least for rapid prototyping. E.g.: Log a...

Any progress on this? Would be really helpful when running watchexec as background process that can garbage-collect itself.

Also: Does it really make sense to only log the failure to create the xfrm policies as a warning? Seems like the network(-attachment) is not usable without that policy so...

The images have been overridden again and caused an outage of one of our services due to changed behaviour (not yet diagnosed). This makes the images unusable for any productive...

I think the root of the problem here is that you are trying to re-use the the version from something else (maybe ModSecurity itself?) to also version the container images....

I think even though that would already been an improvement from the current situation, it is not really ideal as the update process is much less straight forward with that...

For preferring date-strings added to versions from another component (the CRS, I presume), rather then semantically versioning this component independently.