Brooks Townsend
Brooks Townsend
I think that as a foundation for one of the biggest changes we'll make before 1.0.0 this RFC looks great and well thought out. I've tried out the wRPC example...
I moved this issue to Completed for the wasmCloud 1.0 roadmap to signify that the `feat/wrpc` branch has these changes integrated in terms of using wRPC 😄 Other issues like...
For folks looking to take this on, see the TODOs added in #1628 for where we should be defaulting to `~/.wash/keys` 😄
Closed by #1837
I think this is going to get a lot easier when we're stopping/scaling components based on their component ID, rather than looking up an optional name and looking for the...
This is now obsolete that we stop components based on IDs 🚀
To give a high level update of where we are at now in the [feat/wrpc branch](https://github.com/wasmCloud/wasmCloud/tree/feat/wrpc), we've accomplished: - [x] Generate and store component metadata when starting actors and providers...
Just so I don't lose track of it, we're instrumenting traces for custom interfaces but need to make sure that for all of our well-known ones (like HTTP, blobstore, etc)...
One more, I'd love to refactor the Bus trait ```rust /// Identify the target of component interface invocation async fn identify_interface_target( &self, interface: &CallTargetInterface, ) -> anyhow::Result; ``` to both...
A note for onlookers when it comes to wRPC support for interfaces, we plan on supporting the following interfaces in wasmCloud: - WASI 0.2.0 (including `wasi:http`) - Keyvalue (Depending on...