Adding max life connection property to RegistryDatasourceProducer

[Yoni-Weisberg]

This mitigates #5458

[Yoni-Weisberg]

I think the workflow fails are not related to the changes I made. Can you please check?

[jsenko]

hi @Yoni-Weisberg thank you for the PR. It looks unrelated, we'll check.

[carlesarnal]

Hey @Yoni-Weisberg,

Thanks for the contribution. This would for sure fix the issue, but I'm planning a general approach that would solve not only this property but also add the ability to configure any other jdbc-related property. We cannot merge this since that would imply yet another property to maintain in the properties file in the Registry 3.0 lifetime, and we really want to avoid that where possible. As a result, I'm closing this PR, I'll link the new one with the fix as soon as I have it ready.

[Yoni-Weisberg]

Hi @carlesarnal. Thanks for the response
I understand this.
How long will it take to implement the general fix? Currently there is no workaround for this, and the product is effectively broken.

[EricWittmann]

@Yoni-Weisberg for tracking:

• Support generic JDBC properties #5513

[EricWittmann]

I have it scheduled for 3.0.4, hopefully @carlesarnal agrees.

[carlesarnal]

I do agree, yes. It's already solved on main, so it will be included in the next release.