salaboy
> @salaboy sorry for the delays, I am little bit busy, I will try to look into this by EOW. No hurry.. async communications is all good.. don't feel the...
@wangjunyuan89 adding on top @daisuke-yoshimoto comment. This looks like a good contribution, but there are several things that needs to happen for us in order to accept this. First of...
@balsarori can you please check this. It is pointing to 6.x
@balsarori can you please take a look into this and let @ravitadela if he needs to rebase this to 6.x branch or how to proceed?
For the Panel discussion, let's aim to have a more concrete topic. Panels with broad topics like "what is TAG App Delivery?" can be boring and most people don't know...
@artursouza @cicoyle please review. This is the first step to demonstrate OTEL with local development.
@artur-ciocanu I agree, but let's do this in two separate steps.. the Configuration class first and then we can add the fluent buileres to it. I am building an example...
Regarding the ConfigurationSpec interface.. i don't think it makes sense.. if we just have a single configuration CRD that covers a bunch of different topics -> https://docs.dapr.io/operations/configuration/configuration-overview/ Maybe I am...
> @salaboy if it is not too much to ask, could you please rebase your branch. It is outdated. done
I made good progress here.. now traces are propagated in some way for messaging, we need to do the same for the `kvstore` + `bindings` but the messaging side of...