Eventing-SyncGateway: Effect of non-persistent config on function deployment

Sync Gateway 3.x comes with an option of Persistent updates : https://docs.couchbase.com/sync-gateway/current/configuration-overview.html#introduction

Any database changes made using the API endpoints are persisted and survive sync gateway node restarts (this does not apply when running in file-based configuration mode).

From the recent QE tests it has been seen that any db create in Sync Gateway via configuration file is not persisted and is not recorded in the registry.

If it's not recorded in the registry, it cannot be read by Eventing to decide whether to prevent deployment of the function and cannot be used to prevent duplicate mutations.

It essentially means that the work on Eventing-Sync Gateway compatibility is valid only for use cases where configs are persisted.

CC: Adam Fraser For further inputs on this topic to be documented.