Skip to content

Commit 53d6fe7

Browse files
authored
Merge pull request #96822 from banisadr/grid-ce-fixes
cleaning up issues in CE doc
2 parents e148fa9 + 85cf11d commit 53d6fe7

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed

articles/event-grid/cloudevents-schema.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,10 @@ title: Use Azure Event Grid with events in CloudEvents schema
33
description: Describes how to set the CloudEvents schema for events in Azure Event Grid.
44
services: event-grid
55
author: banisadr
6-
manager: timlt
76

87
ms.service: event-grid
98
ms.topic: conceptual
10-
ms.date: 11/07/2018
9+
ms.date: 11/18/2019
1110
ms.author: babanisa
1211
---
1312

@@ -90,7 +89,7 @@ az eventgrid topic create \
9089
--name <topic_name> \
9190
-l westcentralus \
9291
-g gridResourceGroup \
93-
--input-schema cloudeventv01schema
92+
--input-schema cloudeventschemav1_0
9493
```
9594

9695
For PowerShell, use:
@@ -104,7 +103,7 @@ New-AzureRmEventGridTopic `
104103
-ResourceGroupName gridResourceGroup `
105104
-Location westcentralus `
106105
-Name <topic_name> `
107-
-InputSchema CloudEventV01Schema
106+
-InputSchema CloudEventSchemaV1_0
108107
```
109108

110109
The current version of CloudEvents doesn't support batching of events. To publish events with CloudEvent schema to a topic, publish each event individually.
@@ -122,7 +121,7 @@ az eventgrid event-subscription create \
122121
--name <event_subscription_name> \
123122
--source-resource-id $topicID \
124123
--endpoint <endpoint_URL> \
125-
--event-delivery-schema cloudeventv01schema
124+
--event-delivery-schema cloudeventschemav1_0
126125
```
127126

128127
For PowerShell, use:
@@ -133,11 +132,15 @@ New-AzureRmEventGridSubscription `
133132
-ResourceId $topicid `
134133
-EventSubscriptionName <event_subscription_name> `
135134
-Endpoint <endpoint_URL> `
136-
-DeliverySchema CloudEventV01Schema
135+
-DeliverySchema CloudEventSchemaV1_0
137136
```
138137

139138
Currently, you can't use an Event Grid trigger for an Azure Functions app when the event is delivered in the CloudEvents schema. Use an HTTP trigger. For examples of implementing an HTTP trigger that receives events in the CloudEvents schema, see [Use an HTTP trigger as an Event Grid trigger](../azure-functions/functions-bindings-event-grid.md#use-an-http-trigger-as-an-event-grid-trigger).
140139

140+
## Endpoint Validation with CloudEvents v1.0
141+
142+
If you are already familiar with Event Grid, you may be aware of Event Grid's endpoint validation handshake for preventing abuse. CloudEvents v1.0 implements its own [abuse protection semantics](security-authentication.md#webhook-event-delivery) using the HTTP OPTIONS method. You can read more about it [here](https://github.com/cloudevents/spec/blob/v1.0/http-webhook.md#4-abuse-protection). When using the CloudEvents schema for output, Event Grid uses with the CloudEvents v1.0 abuse protection in place of the Event Grid validation event mechanism.
143+
141144
## Next steps
142145

143146
* For information about monitoring event deliveries, see [Monitor Event Grid message delivery](monitor-event-delivery.md).

0 commit comments

Comments
 (0)