itowlson

I'd be keen to see this, although I'm not sure how I feel about including support for particular plugins in templates. That feels like a discussion we should have, though,...

Okay I can do this with a tracing layer but it's all a bit hideously stringy (basically looking for `...wasi::filesystem::types` in the event target and `not-permitted` in the event message)....

The worry with that is still that the meaning of the `middleware` key and the stuff it's meant to do is specific to the HTTP trigger. But good catch as...

@radu-matei The concern is not non-HTTP middleware. Such a thing is _totally_ out of scope unless someone asks for it. The concern is that it how the composition subsystem is...

A specific concern is precomposition in OCI artifacts. By default, Spin performs all composition at `registry push` time (for compatibility with hosts that don't do composition). But how does `spin...

Okay, I started looking at doing it in the HTTP trigger and there's another little nasty: we have an assumption that we can look up `InstancePre`s by component ID. Per-trigger...

All right! I have it working using the trigger: https://github.com/itowlson/spin-middleware-terrifying-nonsense/blob/17e1bf4e23710524fe51ee05689b2ed3f5165609/spin.toml#L14 Please note that "I have it working" is, as ever, code for "it has worked once, in a trivial test...

Updated the `spin-middleware-terrifying-nonsense` testbed to show it modifying the message body (with streaming both in the middleware and at the service). You'll need the https://github.com/dicej/spin/tree/async-fixes branch of Spin to run...

New version: https://github.com/itowlson/spin/tree/http-middleware-take-2 awaits your gasps of dismay. What's changed: * I did OCI. I don't love it, I will never love it, but it works. Has worked. Once. On...

cc @jandubois for visibility