itowlson

Sort of, although that is a custom interface (we have a PR #2486 for wasi-keyvalue but it's stalled on the world rev stuff). But yes, you can back that onto...

@seungjin A plugin is an interesting idea. It could be something the user just remembers to run, or I think @cardoso designed the `spin let` plugin (https://developer.fermyon.com/hub/preview/plugin_spinlet) to allow hooks...

Correct: we weren't able to deliver everything in the time available, and we felt we could do this in a later minor version without breaking backward compatibility.

Okay, looking to define this more closely, particularly in the light of Spin 2 manifest changes. **Requirements** * Put all the manifest stuff related to a subset of the application...

For 3.0 we could adopt `spin.alt` as the documented domain but continue to accept `spin.internal` for backward compatibility.

I don't think it currently exists. If we did this then yes, it would be good to make it available on all triggers, but only HTTP has the header concept:...

My spidey sense is concerned that this one will involve enough bikeshedding, edge cases, and general finickiness that it may not turn out to be a `good-first-issue` after all. (I...

Another poorly-thought-through idea could be to have an expand operator rather than relying on simple text substitution with comma separation within the resulting string. E.g. `allowed_outbound_hosts = ["http://google.com", "{{ my_hosts...

@mikkelhegn I was able to publish with `wkg oci` (and I think now there is a `wkg publish`) and I believe that is compatible with the version of `wasm-pkg-loader` that...

Put another way, we (I) jumped the gun on including registry components before the spec was stable - I totally put my hands up to that.