Michael Gasch

feat: Add rate limiter

2

Closes: #90 Signed-off-by: Michael Gasch

SQL-like Expression Language for patterns

5

In a discussion with a colleague, were I was showcasing `quamina`, he asked whether the `quamina` authors considered SQL(-like) expressions instead of JSON patterns, e.g. using [CloudEvents SQL Expression Language](https://github.com/cloudevents/spec/blob/main/cesql/spec.md)....

Add `GET` and `LIST` APIs for retrieving registered patterns

4

Currently in `quamina` when using the default matcher, i.e. `quamina.New()` there is no way to retrieve the registered patterns, e.g. for debugging, inspection, pattern handling (review/replace during runtime, etc.). The...

WIP: Define schema with cue

3

TODO: - [ ] Discuss folder structure - [ ] Documentation, examples and descriptions - [ ] Add `indicator` - [ ] Add `objectives` Closes: #20 Signed-off-by: Michael Gasch

Define schema in .cue?

5

I think defining the schema using https://cuelang.org/ would bring a lot of benefits at this early stage of the project, e.g.: - Simplified configuration/schema generation via flexible data and schema...

Link to Eventing Data Plane Contract/SPEC

7

**Describe the change you'd like to see** Speaking to many function authors (i.e. Knative Service with Eventing), especially newcomers, most of them are not aware of the underlying data plane...

Allow setting `KO_DOCKER_REPO` in `.ko.yaml`

12

Based on a Twitter [conversation](https://twitter.com/mattomata/status/1498527641762091016?s=20&t=BofE5KKl1XeD5cMRSToPuQ), it was raised whether `KO_DOCKER_REPO` should also be a configuration option in `.ko.yaml` (mainly for consistency purposes). IMHO since this is not a build but...

Define common build tags to consume in `.ko.yaml`

3

Since `.ko.yaml` is likely going to be used for more CI automation and releasing artifacts, it would be great to have access to common build variables, e.g. `date/time` (RFC3339), `commit`...