Brooks Townsend
Brooks Townsend
Only remaining work here is to validate traces and add a test for `wash call`.
WIth #1869 , we're done!
Yep that's right @cdmurph32 ! Fuzzing on the CLI is nice to make sure we can't just straight up break the runtime with a malformed string. Fuzzing on the control...
@cdmurph32 getting closer here, in https://github.com/wasmCloud/wasmCloud/pull/1588 I refactored a bunch of the handlers to return strongly typed data. More refactors to come for the code but just a note on...
Just a note that in a recent PR we did rename this to `component_scaled`, so make sure to use that event 😄
I'm a huge fan of this request. From the wadm side it's just accepting the name of the manifest on the API, so this should be solved on the `wash`...
@UtkarshUmre I'm not @protochron, but i can point you in the right direction 😄 So when you launch wasmCloud development infrastructure with `wash up`, we accept a couple NATS parameters...
Sounds great @Aditya1404Sal ! Since it would go stale, I'll assign you to it 😄
We updated these as a part of the 1.0 documentation 🚀
To be annoying, I only see the registry option in https://wasmcloud.com/docs/reference/config#type-config---component and not the credentials option, so once it's added to wasmcloud.com I think it can be marked done!