Pablo Mercado

Avoid event loops when Triggers is configured to a Sink that returns new events

4

**Problem** A sink receiving a CloudEvent has the choice of replying with a new event, which enables scenarios that query external systems or do transformations. It is expected that the...

After executing load tests it seems that the safest bet for most common scaling scenarios is using RPS metrics. Concurrency metrics are more customizable, but it might be harder to...

Replier: improve response error types

2

The [replier](https://github.com/triggermesh/triggermesh/blob/d60ec281c0e512ed5ddb139746fd7c19ce67fe00/pkg/targets/adapter/cloudevents/replier.go#L60) object helps composing replies at targets. Functions `Ok` and `Error` at the replier are used on success and error scenarios: - `Ok` will set a new type to...

Move routing to flow API

1

This is a breaking change for an alpha versioned items, should be done ASAP. Move routing `routing.triggermesh.io` items to `flow.triggermesh.io` to keep API groups as agreed.

WebhookSource should reply with 204 when returning an empty response to caller.

All components of a bridge should make their best effort to be deleted and avoid getting stuck. This AzureBlobStorageSource object is stuck while deleting: ```yaml apiVersion: sources.triggermesh.io/v1alpha1 kind: AzureBlobStorageSource metadata:...

HTTPSource should implement common webhook verifications by sources. The problem is that they might differ slightly on the process or where the signed payload is informed, but we can come...