Details
-
Bug
-
Resolution: Fixed
-
Major
-
3.1.1
-
Security Level: Public
-
None
-
CBG Sprint 137
-
2
Description
There's a bug in bootstrapContext.GetDatabaseConfigs. When both legacy (3.0) and current configs are found, the current config is intended to be used. Instead, the bug here is causing the legacy config to be returned, which ends up being used by the caller (as it's the last entry in the slice for the key). https://github.com/couchbase/sync_gateway/blob/master/rest/config_manager.go#L363