You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently holding off on adding support for enabling IAM auth through the url as this doesn't seem to be working as expected for the R2DBC workflow. Extra options parsed from the url are automatically typed as String so when GcpConnectionFactoryProvider#createFactory in the Cloud SQL Java socket factory library calls (Boolean)connectionFactoryOptions.getValue(ENABLE_IAM_AUTH) this results in an error.
I think this will have to be a change in GcpConnectionFactoryProvider.
Even when the limitation in R2DBC gets addressed with some new API, the socket factory will still have to switch to using the new API.
This seems to be blocked as described below:
Currently holding off on adding support for enabling IAM auth through the url as this doesn't seem to be working as expected for the R2DBC workflow. Extra options parsed from the url are automatically typed as
String
so when GcpConnectionFactoryProvider#createFactory in the Cloud SQL Java socket factory library calls(Boolean)connectionFactoryOptions.getValue(ENABLE_IAM_AUTH)
this results in an error.Originally posted by @mpeddada1 in #772 (comment)
The text was updated successfully, but these errors were encountered: