firebase-functions icon indicating copy to clipboard operation
firebase-functions copied to clipboard

Published 20 hours ago • verified publisher icon firebase

Unable to connect Cloud SQL with Firebase Functions V2

Open service-paradis opened this issue 2 years ago • 1 comments

Related issues

[REQUIRED] Version info

node: 16.16.0

firebase-functions: 3.22.0

firebase-tools: 11.4.0

firebase-admin: 11.0.1

[REQUIRED] Test case

I'm trying to migrate a Firebase Functions from V1 to V2 to try beta features. It looked like Cloud SQL connection are not yet supported, but did not find anything in the documentation about it.

[REQUIRED] Steps to reproduce

  1. Create a Firebase Functions that connects to a Cloud SQL database using a socket path like /cloudsql/INSTANCE_CONNECTION_NAME.
  2. Call this function
  3. Get an ENOENT error that were not received using V1

[REQUIRED] Expected behavior

I expected that Cloud SQL would be available to the function.

[REQUIRED] Actual behavior

I got ENOENT error while trying to connect to the database. According to https://cloud.google.com/sql/docs/mysql/connect-run?hl=fr#console, it looks like I would need to add a Cloud SQL connection to my service. I'm not sure how to this while deploying my function using Firebase Tools.

I tried adding the Cloud SQL connection using the console, but it fails with this error: image

I tried using the cli with something like gcloud run services update api --add-cloudsql-instances=INSTANCE_CONNECTION_NAME, but it gives me the sdame kind of errors like:

Deployment failed
ERROR: (gcloud.run.services.update) Image 'us-central1-docker.pkg.dev/PROJECT_NAME/gcf-artifacts/api:version_1' not found.

Were you able to successfully deploy your functions?

Yes, without any errors. The function itself seems to be working as expected, but it cannot connect to a Cloud SQL instance.

If this is possible, the information is missing in the doc.

If this is not yet possible using the beta functions, the information is also missing from the doc.

service-paradis avatar Aug 31 '22 20:08 service-paradis

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

google-oss-bot avatar Aug 31 '22 20:08 google-oss-bot

Unfortunately, because we clean up your docker image after deploy to save your money, you cannot edit the Run service without providing a new image. This feature should work and we'll look into it.

inlined avatar Oct 18 '22 12:10 inlined

@inlined Thank you for the follow up! Glad to know it will be supported!

service-paradis avatar Oct 18 '22 19:10 service-paradis

Any updates on this @inlined? I'm facing the same issue.

Have you found a workaround @service-paradis?

metadiego avatar Dec 27 '22 07:12 metadiego

I think this feature request is duplicate of https://github.com/firebase/firebase-tools/issues/4932. Will use the other as it's in the more appropriate location. Feel free to re-open or to file another issue if I missed something.

taeold avatar Dec 29 '22 23:12 taeold

I think this feature request is duplicate of firebase/firebase-tools#4932. Will use the other as it's in the more appropriate location. Feel free to re-open or to file another issue if I missed something.

@taeold I believe there's a difference between the two situations. When I attempted to manually update the service, I encountered an artifact error. However, ideally, we should be able to connect to a Cloud SQL database without the need to manually update services. Currently, Firebase functions version 1 can connect to Cloud SQL databases automatically. I would expect that version 2 could also connect with minimal effort required.

service-paradis avatar Feb 24 '23 00:02 service-paradis

@taeold In fact, I'm not sure why the title have been changed since my issue is being unable to connect to Cloud SQL with Firebase Functions V2.

service-paradis avatar Mar 02 '23 13:03 service-paradis