You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sdk/eventgrid/azure-eventgrid/CHANGELOG.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,10 @@
8
8
- EventGridClient `send` can be used for both Event Grid Namespace Resources and Event Grid Basic Resources.
9
9
- Added a kwarg `level` in the EventGridClient constructor. The default value is `Standard` which creates a client for an Event Grid Namespace Resource.
10
10
11
-
### Breaking Changes
12
-
- Removed the `AcknowledgeOptions`,`ReleaseOptions`, `RejectOptions`, and `RenewLockOptions` models. `lock_tokens` can now be specified as a `kwarg` on the operation.
13
-
- Renamed `publish_cloud_events` to `send`.
11
+
### Breaking Changes
12
+
13
+
- Removed the `AcknowledgeOptions`,`ReleaseOptions`, `RejectOptions`, and `RenewLockOptions` models. `lock_tokens` can now be specified as a `kwarg` on the operation.
az eventgrid topic --create --location <location> --resource-group <resource-group-name> --name <resource-name>
71
-
```
72
-
73
-
#### Create an Event Grid Basic Domain
74
-
75
-
```
76
-
az eventgrid domain --create --location <location> --resource-group <resource-group-name> --name <resource-name>
77
-
```
78
-
79
55
### Authenticate the client
80
56
In order to interact with the Event Grid service, you will need to create an instance of a client.
81
57
An **endpoint** and **credential** are necessary to instantiate the client object.
@@ -176,7 +152,7 @@ An **[event](https://docs.microsoft.com/azure/event-grid/concepts#events)** is t
176
152
177
153
Event Grid supports multiple schemas for encoding events.
178
154
179
-
#####System Topics
155
+
#### System Topics
180
156
A **[system topic](https://docs.microsoft.com/azure/event-grid/system-topics)** in Event Grid represents one or more events published by Azure services such as Azure Storage or Azure Event Hubs. For example, a system topic may represent all blob events or only blob creation and blob deletion events published for a specific storage account.
181
157
182
158
The names of the various event types for the system events published to Azure Event Grid are available in `azure.eventgrid.SystemEventNames`.
@@ -205,24 +181,10 @@ The following formats of events are allowed to be sent to an EventGrid Namespace
205
181
206
182
Please have a look at the [samples](https://github.com/Azure/azure-sdk-for-python/tree/feature/eventgrid/sdk/eventgrid/azure-eventgrid/samples) for detailed examples.
207
183
208
-
209
184
## Event Grid on Kubernetes with Azure Arc
210
185
211
186
Event Grid on Kubernetes with Azure Arc is an offering that allows you to run Event Grid on your own Kubernetes cluster. This capability is enabled by the use of Azure Arc enabled Kubernetes. Through Azure Arc enabled Kubernetes, a supported Kubernetes cluster connects to Azure. Once connected, you are able to install Event Grid on it. Learn more about it [here](https://docs.microsoft.com/azure/event-grid/kubernetes/overview).
212
187
213
-
### Support for CNCF Cloud Events
214
-
215
-
Starting with v4.7.0, this package also supports publishing a CNCF cloud event from https://pypi.org/project/cloudevents/. You would be able to pass a CloudEvent object from this library to the `send` API.
216
-
217
-
```python
218
-
219
-
from cloudevents.http import CloudEvent
220
-
221
-
event = CloudEvent(...)
222
-
223
-
client.send(event)
224
-
```
225
-
226
188
## Examples
227
189
228
190
The following sections provide several code snippets covering some of the most common Event Grid tasks, including:
@@ -510,39 +472,39 @@ This project has adopted the [Microsoft Open Source Code of Conduct][code_of_con
0 commit comments