Oldřich Jedlička

The configuration has changed also due to update to `lua-resty-session-4.x` in `lua-resty-openidc-1.8.0`, so I recommend checking [sample configuration](https://github.com/zmartzone/lua-resty-openidc?tab=readme-ov-file#sample-configuration-for-google-signin), especially the part mentioning `session_opts`, particularly the `secret` value 😊.

I prepared a fix for this in #3373 - to read POD's env variables defined in ConfigMaps and Secrets. With my fix the `JAVA_TOOL_OPTIONS` value is correctly merged - OTEL's...

Reported again to Lexilla https://github.com/ScintillaOrg/lexilla/issues/326

Added few more tests for user-added `LoggingHandler` - they are not touched by instrumentation.

Updated changelog to refer to this pull request.

I have added a Proof-of-Concept commit to prove that `LoggingHandler` can be moved out of SDK: 1. Root logger instrumentation is done in the logging instrumentation, not in the SDK....

@lzchen > A couple of questions as I seem to be confused about the issue and the proposed solution. > > 1. Can you provide sample code in the description...

Any update, please? I can finish the PoC - just let me know if that is acceptable, I can prepare it. 😊

That is not how it works. `openidc_get_path` just strips the `?query_parameters` part from the URI. The code which switches to the response handling part is this: ```lua local path =...

It seems the code lines do not align with the `lua-resty-openidc` v1.7.2 tag. Are you sure about the versions or do you have custom modifications of the code to do...