Matthias Wessendorf
Matthias Wessendorf
/test reconciler-tests
/test reconciler-tests
For the `http` we also have a different one: * https://github.com/knative/func/blob/main/templates/go/http/handle.go#L11 but that's a bit different, so I think I am more wondering about the cloud events case
I was wondering same: Why defaulting to Structured CloudEvent ? Looking at some demos: https://docs.dapr.io/developing-applications/building-blocks/pubsub/pubsub-cloudevents/#example I see structured CE usage like: ``` curl -v -X POST http://localhost:3501/v1.0/publish/orderpubsub/orders -H "Content-Type: application/cloudevents+json"...
That's a good point. HA could be use to apply for all deployments, as is, but workload wins as an override? Or is `workloads` the way to go, b/c you...
I like the pirate mascot !
Was there any outcome on that discussion?
Any thoughts on the API proposed here/anything you would change? ``` attributes: - name: "type" value: "event.{requestStatus}.foo" required: true ... variables: - name: "requestStatus" regex: "[a-zA-Z]" example: "request.failed" ``` so...
> Yeah, I think that makes sense to me, we might also want to verify that the example in the variable is allowable based on the pattern for the variable...