Create a schema for eventing handler structure

Description

Currently, there is no documented schema for what goes into a handler body. This needs to change as the product matures, and so the first step is to create a schema for the body structure. As a first step towards validating schema, the unit tests (only) should start enforcing schema. Also remove internal fields so the handler body contains only the user's intent.

Components

Affects versions

Fix versions

Labels

Environment

None

Link to Log File, atop/blg, CBCollectInfo, Core dump

None

Release Notes Description

None

Activity

CB robot October 15, 2020 at 2:47 PM

Build couchbase-server-7.0.0-3428 contains eventing commit a1a0986 with commit message:
: Fix schema issues and ensure stricter validation

CB robot September 9, 2020 at 11:11 AM

Build couchbase-server-7.0.0-3060 contains eventing commit 2f11170 with commit message:
: Create a schema for eventing handler structure

Sriram Melkote September 9, 2020 at 9:01 AM

Initial schema has been committed. Future patchsets will refine these. Also, the schema will be enforced in REST entry points progressively over the course of Cheshire Cat development.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Is this a Regression?

Unknown

Triage

Untriaged

Story Points

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created August 31, 2020 at 9:39 AM
Updated June 17, 2021 at 10:08 PM
Resolved September 9, 2020 at 9:01 AM
Instabug