Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-43762

[BP MB-40810] - Allow deploy "everything" and "from now" to be a setting per Function

    XMLWordPrintable

Details

    • Untriaged
    • 1
    • Unknown

    Description

      The UI always defaulting to "everything" is a wrong for certain use cases. Today, when we export, we always set it to "everything" in the exported file, and when deploy, we always default to "everything".

      Currently we set "dcp_stream_boundary": "everything" when we export Functions but it's not doing anything useful once the handler is exported. And we always by default do a deploy from everything, we allow this to be overridden in the UI.  An improvement would be to allow the "default" to come from athe Function's settings.

      Some customers always deploy from now, others mostly deploy form everything and I imagine we will find a "mix" in the future.

      The UI should allow a "default" preference on a per handler basis to be configured in the settings as an option (and it could be changed via REST or CLI)

      • "dcp_stream_boundary": "everything"
      • "dcp_stream_boundary": "from_now" (not sure what now should be)

      Should be a required setting, like other settings for example "source bucket"

      The benefit is that this will cut down on repetitive work and mistakes made by customers who have to deploy from now.  In the UI customers should be able to override the configured setting when they confirm the deployment (but this should not be sticky).

      Attachments

        Issue Links

          For Gerrit Dashboard: MB-43762
          # Subject Branch Project Status CR V

          Activity

            Build couchbase-server-6.6.2-9509 contains eventing commit d2614a8 with commit message:
            MB-43762: Refactor DCP Feed boundary and Deprecate 'from_prior'

            build-team Couchbase Build Team added a comment - Build couchbase-server-6.6.2-9509 contains eventing commit d2614a8 with commit message: MB-43762 : Refactor DCP Feed boundary and Deprecate 'from_prior'

            Build couchbase-server-6.6.2-9526 contains eventing commit 81c9908 with commit message:
            MB-43762 MB-43461: Enable runtime settings only

            build-team Couchbase Build Team added a comment - Build couchbase-server-6.6.2-9526 contains eventing commit 81c9908 with commit message: MB-43762 MB-43461 : Enable runtime settings only

            Build couchbase-server-6.6.2-9534 contains eventing commit a7a9459 with commit message:
            MB-43762: Enable Default Boundary during Add Function

            build-team Couchbase Build Team added a comment - Build couchbase-server-6.6.2-9534 contains eventing commit a7a9459 with commit message: MB-43762 : Enable Default Boundary during Add Function

            Option is available in UI for deploy "Everything" and "From now"

            chanabasappa.ghali Chanabasappa Ghali added a comment - Option is available in UI for deploy "Everything" and "From now"

            Build couchbase-server-6.6.2-9580 contains eventing commit aa20c63 with commit message:
            MB-43762: Get rid of errors in JS console

            build-team Couchbase Build Team added a comment - Build couchbase-server-6.6.2-9580 contains eventing commit aa20c63 with commit message: MB-43762 : Get rid of errors in JS console

            People

              vinayaka.kamath Vinayaka Kamath (Inactive)
              jeelan.poola Jeelan Poola
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty