KratkyZobak

It seems, there is lot miscommunication in this thread. tl;dr; - I belive, there is need to support `ICredentialsProvider` from RabbitMQ.Client instead of just passing `Username` and `Password`. When using...

> I only see one implementation of the credentials provider for .NET, and that's basic (username/password). I'm not sure if a new one is coming, but for now that's all...

This is some sort of black magic? I would vote to keep KISS principle in project and propose rejecting this PR.

Problem is only in mindset. Of course I can handle solving this by connection factory and/or decorator above current Connection class, where I would re-implement connection laziness. I belive, this...

Solved by https://github.com/nette/database/commit/abd38ef93eb366e4e661e0012343cc3551f58a17 (moving PDO::connect call from Connection to Driver class). Driver is injectable to Connection, so we can create own Driver without mangling with Connection.

`azure.workload.identity/client-id` annotation should not be required to modify. You should specify `clientId` in `podIdentity.identityId` for each specific `TriggerAuthentication` resource.

After https://github.com/nette/database/commit/abd38ef93eb366e4e661e0012343cc3551f58a17 this PR would not be needed (we can inject own driver, which can handle dynamic password and ignore the one from configuration). @dg will https://github.com/nette/database/commit/abd38ef93eb366e4e661e0012343cc3551f58a17 be available in...

Same problem here. We are using JWT tokens to authorize against Azure MySQL Flexible Server. Our username and token combined are over 4k for some identities. Problem is in this...