itowlson

Thanks for sharing this idea - very intriguing! I can definitely see the attraction to having an embedded graph database in the same way as we have SQLite. The challenge...

@vdice I reckon this one is no longer very relevant - anyone who is going to migrate off v1 has likely done so by now. So I'm closing it, but...

I wouldn't want to see these in `spin-app`, which relates specifically to the runtime environment and is bound to `spin-core` and `wasmtime`, but agree they may be reusable (`cloud-plugin` has...

My feelings about that are very mixed. On the one hand, yes, it could be a powerful enabler of consistent behaviour and experience across different Spin runtime hosts (for hosts...

This is at least partly addressed by #721.

This is potentially relevant to #2555, although I'm not sure the strategy of requiring an environment variable would fit with Rancher Desktop's needs. That feels like it's closer to the...

also cc @jandubois for visibility - looking at the issue, Rancher's needs are broader than just plugins, but it does sound like the environment variable approach would meet their needs

I'm not sure what "the logic to detect this file" refers to. As you know, you can pass the path of the runtime config file to the trigger object. At...

@kate-goldenring Maybe we need to have a chat (and/or put together a document) to align our understandings. To me, the runtime config cannot be in the OCI artifact, because OCI...

In Spin 3, you can use `wasi-config` including the `get-all` function. Is that an option for you? Caveats: * May take a bit of time to flow through to other...