Webhook payload changed

David Zeidman

Is there any particular reason Blackbaud that the payload for the CloudEventsV10Event payload has suddenly changed!

From webhook monitor:

Constituent record changed

Received November 8, 2023 3:19 PM

Record ID None found.

{

"id": "2cc8d99d-ed75-41b5-a46b-3b8c76460bb4",

"source": "OAWUE4CRJJJW25KKNFCS2MDDNZTUMUDKNZFGC5Y",

"type": "com.blackbaud.constituent.change.v1",

"data": {

"Id": "16871",

"AddedById": 56,

"LastChangedById": 56

},

"time": "2023-11-08T15:19:04.8461576+00:00",

"specversion": "1.0",

"subject": "/environments/p-BpQJSmuJiE-0cngFPjnJaw"

}

From the documentation:

Constituent record changed

com.blackbaud.constituent.change.v1

Event data properties	Description	Data type
id	Constituent record identifier	string
added_by_id	Identifier of the user who added the record	int
last_changed_by_id	Identifier of the user who last changed the record	int

All of a sudden our code broke because the data properties have changed case and changed format.

@Chris Rodgers Any thoughts?

Chris Rodgers

Hey, @David Zeidman. We had a deployment on Friday that updated some common eventing/messaging libraries. We're still looking into it, but I suspect that this inadvertently changed the serialization of the event data we publish and likely updated our tests as well to expect this serialization, so they didn't catch the change. We're actively rolling back the change, and you should see the former payload schema resolving in 5-10 minutes. Thank you for bringing it to our attention. We'll have a fix and update our tests to divorce them from this shared serialization issue so a similar change will be caught in the future.

Update: We've completed the rollback. We apologize for the unexpected change. We'll put more safeguards in place to ensure this doesn't happen again.

David Zeidman

@Chris Rodgers Thanks for rolling this back so quickly. Appreciated.