Frank Koornstra

Pong @yanglei99 @kkonstantine @levzem @dosvath

Went on a sabbatical for 3 months and still :joy: I thought for a moment that this project was abandoned all together but there's still stuff merged few days ago....

If you're still searching for a platform-type of solution, take a look at Apache Flink. You get pretty much access to the bare-bones Elasticsearch API so you can do whatever...

@antoniandre any chance of this happening? I've looked into the code but it's too complicated for me to open a PR, sorry! If you can drop a hint on how...

Nice! +1

For my use case, on the plugin on the route. Globally would be nice but I'd rather have more granular options

Thanks for the tip. I'm deploying Apisix through the official Helm chart however and I don't think it has any facilities for this. Only thing I can find is this:...

Thanks for that. I'll wait for the next release to include it since Helm chart 2.1.0 does not contain that just yet but good to know that it's coming :+1:

Being able to determine the ID beforehand - let's say `user-management` - would save us a lot of trouble because we can rely on a naming convention and we'd now...

For clarity: I'm not suggesting using the actual `metadata.name` of the k8s resource for its id, but instead introduce a (nullable) field in the spec, maybe `spec.route_id` that could be...