🐛 [firestore-send-email] Reconfiguring extension leads to "Function location processQueue would be changed during update" error

[hongaar]

Describe your configuration

• Extension name: firestore-send-email
• Extension version: 0.1.34
• Configuration values:

{
  "DEFAULT_FROM": "info@examtraining.online",
  "MAIL_COLLECTION": "mail",
  "SMTP_CONNECTION_URI": "smtps://postmaster%40mg.examtraining.online@smtp.eu.mailgun.org:465",
  "SMTP_PASSWORD": "projects/{id}/secrets/firestore-send-email-SMTP_PASSWORD/versions/1",
  "TTL_EXPIRE_TYPE": "week",
  "TTL_EXPIRE_VALUE": "1"
}

Describe the problem

I want to update some parameters from the Extensions GUI in the Firebase Console. When I click Reconfigure extension, make my changes, and then click Save, nothing happens in the GUI. I can see a request is made for https://firebaseextensions.clients6.google.com/v1beta/projects/examtraining-c20cd/instances/firestore-send-email?updateMask=config.params,config.system_params,config.allowed_event_types,config.eventarc_channel&alt=json&key={key} with the updated params in the payload. This request runs into a 400 response with this body:

{
  "error": {
    "code": 400,
    "message": "Function location \"processQueue\" would be changed during update, which can have unexpected results. To change instance location, create a new instance instead.",
    "status": "INVALID_ARGUMENT"
  }
}

After clicking Cancel, this message occurs in the Extensions GUI:

Error saving configuration

Be aware that a parameter misconfiguration might have caused some extension resources to not successfully deploy.

Use the details below to help resolve this error, then retry configuring the extension. If you continue to get this error, we recommend uninstalling the extension to remove any extension resources that might be deployed.

There was an unknown error while processing the request.

Not sure if this is something which can be fixed in the extension code or is a generic problem with the Extensions GUI and should be addressed to the Firebase team.

Steps to reproduce:

I first updated the TTL_EXPIRE_TYPE successfully, but after this, subsequent changes to any other param resulted in this error.

Expected result

Updated params

Actual result

Error message