mirror of https://github.com/dapr/docs.git
Merge branch 'v0.11' into orizohar-patch-2
This commit is contained in:
commit
2a0ed80f72
|
@ -49,9 +49,9 @@ Your handler implementation can include any inbound logic, outbound logic, or bo
|
||||||
func GetHandler(metadata Metadata) fasthttp.RequestHandler {
|
func GetHandler(metadata Metadata) fasthttp.RequestHandler {
|
||||||
return func(h fasthttp.RequestHandler) fasthttp.RequestHandler {
|
return func(h fasthttp.RequestHandler) fasthttp.RequestHandler {
|
||||||
return func(ctx *fasthttp.RequestCtx) {
|
return func(ctx *fasthttp.RequestCtx) {
|
||||||
//inboud logic
|
// inboud logic
|
||||||
h(ctx) //call the downstream handler
|
h(ctx) // call the downstream handler
|
||||||
//outbound logic
|
// outbound logic
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
|
@ -57,7 +57,7 @@ As seen above, you invoked the `/binding` endpoint with the name of the binding
|
||||||
The payload goes inside the mandatory `data` field, and can be any JSON serializable value.
|
The payload goes inside the mandatory `data` field, and can be any JSON serializable value.
|
||||||
|
|
||||||
You'll also notice that there's an `operation` field that tells the binding what you need it to do.
|
You'll also notice that there's an `operation` field that tells the binding what you need it to do.
|
||||||
You can check [here]({{< ref bindings >}}) which operations are supported for every output binding.
|
You can check [here]({{< ref supported-bindings >}}) which operations are supported for every output binding.
|
||||||
|
|
||||||
|
|
||||||
## References
|
## References
|
||||||
|
|
|
@ -49,9 +49,9 @@ Every binding has its own unique set of properties. Click the name link to see t
|
||||||
| Name | Input<br>Binding | Output<br>Binding | Status |
|
| Name | Input<br>Binding | Output<br>Binding | Status |
|
||||||
|------|:----------------:|:-----------------:|--------|
|
|------|:----------------:|:-----------------:|--------|
|
||||||
| [Azure Blob Storage]({{< ref blobstorage.md >}}) | | ✅ | Experimental |
|
| [Azure Blob Storage]({{< ref blobstorage.md >}}) | | ✅ | Experimental |
|
||||||
| [Azure EventHubs]({{< ref eventhubs.md >}}) | ✅ | ✅ | Experimental |
|
|
||||||
| [Azure CosmosDB]({{< ref cosmosdb.md >}}) | | ✅ | Experimental |
|
| [Azure CosmosDB]({{< ref cosmosdb.md >}}) | | ✅ | Experimental |
|
||||||
|
| [Azure Event Grid]({{< ref eventgrid.md >}}) | ✅ | ✅ | Experimental |
|
||||||
|
| [Azure Event Hubs]({{< ref eventhubs.md >}}) | ✅ | ✅ | Experimental |
|
||||||
| [Azure Service Bus Queues]({{< ref servicebusqueues.md >}}) | ✅ | ✅ | Experimental |
|
| [Azure Service Bus Queues]({{< ref servicebusqueues.md >}}) | ✅ | ✅ | Experimental |
|
||||||
| [Azure SignalR]({{< ref signalr.md >}}) | | ✅ | Experimental |
|
| [Azure SignalR]({{< ref signalr.md >}}) | | ✅ | Experimental |
|
||||||
| [Azure Storage Queues]({{< ref storagequeues.md >}}) | ✅ | ✅ | Experimental |
|
| [Azure Storage Queues]({{< ref storagequeues.md >}}) | ✅ | ✅ | Experimental |
|
||||||
| [Azure Event Grid]({{< ref eventgrid.md >}}) | ✅ | ✅ | Experimental |
|
|
||||||
|
|
|
@ -1,4 +1,3 @@
|
||||||
|
|
||||||
---
|
---
|
||||||
type: docs
|
type: docs
|
||||||
title: "Apple Push Notification Service binding spec"
|
title: "Apple Push Notification Service binding spec"
|
||||||
|
|
|
@ -63,7 +63,7 @@ Three different event types are available:
|
||||||
- Delete : Only the `oldVal` field is populated, `newVal` field is an empty `v1.Event`, `event` is `delete`
|
- Delete : Only the `oldVal` field is populated, `newVal` field is an empty `v1.Event`, `event` is `delete`
|
||||||
- Update : Both the `oldVal` and `newVal` fields are populated, `event` is `update`
|
- Update : Both the `oldVal` and `newVal` fields are populated, `event` is `update`
|
||||||
|
|
||||||
## Required permisiions
|
## Required permissions
|
||||||
|
|
||||||
For consuming `events` from Kubernetes, permissions need to be assigned to a User/Group/ServiceAccount using [RBAC Auth] mechanism of Kubernetes.
|
For consuming `events` from Kubernetes, permissions need to be assigned to a User/Group/ServiceAccount using [RBAC Auth] mechanism of Kubernetes.
|
||||||
|
|
||||||
|
@ -105,4 +105,4 @@ roleRef:
|
||||||
- [Bindings building block]({{< ref bindings >}})
|
- [Bindings building block]({{< ref bindings >}})
|
||||||
- [How-To: Trigger application with input binding]({{< ref howto-triggers.md >}})
|
- [How-To: Trigger application with input binding]({{< ref howto-triggers.md >}})
|
||||||
- [How-To: Use bindings to interface with external resources]({{< ref howto-bindings.md >}})
|
- [How-To: Use bindings to interface with external resources]({{< ref howto-bindings.md >}})
|
||||||
- [Bindings API reference]({{< ref bindings_api.md >}})
|
- [Bindings API reference]({{< ref bindings_api.md >}})
|
||||||
|
|
Loading…
Reference in New Issue