Private API always have minimum instance on Google Cloud

[greghesp]

Can we access your project?

• [X] I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

When deploying private API, minimum instance of 1 is set. This is undocumented, and doesn't make sense. It has cost implications, and a non private API does not do this.

In addition, if you try changing your function deploy settings and attempt to leave the minimum/maximum instances as Flutterflow deployed it, GCM flags an error:

Expected Behavior

Private API acts the same as Public API and does not add a minimum instance

Steps to Reproduce

1) Create API call 2) Deploy as Private APIs 3) Go to Google Console > select function and view Detail. A minimum instance of 1 is set, with an error

Reproducible from Blank

• [X] The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4ez/Llw4x2pbwA7qqNbMJagSQUH1w6UOYvku0bFQwbCIDwE4oteOjxP2FoUtfiTAk7L1mkoD4dp9LShuzEA+UqYCqBbJ84+LtyTTuWUj+6V8mWDJDpfkZSL5tJJVPC0Z2zsQhRCPt2WGRk2lOMOPKiTgPdHu/uIVYwRPH/OoX4nVGpQ0SLb3kNh1JWeC

Visual documentation

Environment

- FlutterFlow version: 4.1.72
- Platform: MacOS Desktop
- Browser name and version: 125.0.6422.112
- Operating system and version affected: n/a

Additional Information

No response

[msusviela]

I was able to reproduce the issue, I will send it to the ENG team so they can work on this!

[damianfraire]

I found the same behavior, in both V1 and V2 cloud functions created through private API setting. V1 is the one displayed above with an error highlighted because minimum > maximum. The V2 version, that is resolved but still is always minimum 1, causing unexpected cloud function compute engine idle costs in google environment. I have to manually modify the cloud functions definitions every time I deploy an update to the private APIs, sometimes I forget and luckily I set billing alerts but still getting charged unnecessarily.