Uploaded image for project: 'Couchbase Gateway'
  1. Couchbase Gateway
  2. CBG-3462

[3.1.2 backport] Sync Gateway should not use 3.0 config when 3.1 config is present

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 3.1.2
    • 3.1.1
    • SyncGateway
    • 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

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            adamf Adam Fraser
            adamf Adam Fraser
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty