From 4f685b21c25524025f36decee60cd6d7d396d548 Mon Sep 17 00:00:00 2001 From: Devin Stein Date: Thu, 12 Dec 2019 11:21:39 -0800 Subject: [PATCH] fix: userPayload JSON should not be a string (#430) --- examples/event-sources/calendar.yaml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/examples/event-sources/calendar.yaml b/examples/event-sources/calendar.yaml index 8d376526bf..12c9dfe3e7 100644 --- a/examples/event-sources/calendar.yaml +++ b/examples/event-sources/calendar.yaml @@ -17,14 +17,16 @@ spec: schedule: "30 * * * *" # userPayload is a static string that will be send to the the sensor with each event payload # whatever you put here is blindly delivered to sensor. - userPayload: "{\"hello\": \"world\"}" + # access in resourceParameters or templateParameters via the path userPayload.hello + userPayload: {"hello": "world"} schedule-in-specific-timezone: # creates an event every 20 seconds interval: "20s" # userPayload is a static string that will be send to the the sensor with each event payload # whatever you put here is blindly delivered to sensor. - userPayload: "{\"hello\": \"world\"}" + # access in resourceParameters or templateParameters via the path userPayload.hello + userPayload: {"hello": "world"} # timezone # more info: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones timezone: "America/New_York"