However, it would be nice to have a settings panel entry to specify an alternate default port. Even a global setting that isn't instance-specific would be helpful. Without this, you have to remember and manually respecify the alternate port each time you open a connection.
While the documentation entry talks about this as an issue with multiple connections to different instances, it's also a persistent and unresolvable conflict if you have a local copy of the target database running on the engine's default port.
Thanks @bkoski this is a valid point on default port number for a popular database type being busy. We will let you know when a more flexible solution is available in Cloud Code.
The Cloud SQL Proxy integration in DataGrip is very nice and makes the process of setting up these connections much smoother.
I understand that auto-resolving port conflicts is a known issue and likely not something the plugin wants to get into the business of solving.
However, it would be nice to have a settings panel entry to specify an alternate default port. Even a global setting that isn't instance-specific would be helpful. Without this, you have to remember and manually respecify the alternate port each time you open a connection.
While the documentation entry talks about this as an issue with multiple connections to different instances, it's also a persistent and unresolvable conflict if you have a local copy of the target database running on the engine's default port.