Loïc Mathieu

@brunobat we can move all configuration properties to the main otel extension and consume this property inside the logs extension. Or we can do the opposite, move what is needed...

OK, there is not a log of code to support logs so it could easily be merged into the existing otel extension.

@brunobat of course you can add commits to my PR, be my guest ;) For now, this didn't work as the Log tracer uses OkHttp which is no longer in...

In fact it can be done more elegantly by injecting an `Instance` and use instance.isAvailable(). There is multiple places where this can be done as this issue exists in multiple...

Yes, the current HTTP tasks can be moved to the core without needed any additional library. We can also move them to a dedicated plugin for better visibility.

Juts noticed that, it seems to be related to Cloud Logging.

Firebase messaging is not supported for the moment. If you have GraalVM native image reflection configuration for it, the best is to open an issue upstream (should b https://github.com/firebase/firebase-admin-java) as...

So it's not only on Windows as I was told. Can you try with something very simple like a Shell task that try to write in a file? ``` id:...

And if you call `pwd` the working directory is correctly created? ```yaml id: old-shell namespace: myteam tasks: - id: shell type: io.kestra.plugin.scripts.shell.Commands commands: - pwd ```

I tried on Docker Swarm and it works, it should be some permission issue. I notice that you mount `/tmp:/tmp/kestra-wd` mounting `/tmp` can be a bit blunt as there can...