Mario Vejlupek

@anguslees yes! that would solve another issue we have. We want to allow developers to exchange encrypted credentials so other side get sealed credentials and all they have to do...

well win of [web-component-tester](https://github.com/Polymer/web-component-tester) over [bore](https://github.com/treshugart/bore) is simplicity of setup. All you have to do is to create test harness file and that's all. It's ugly and huge black box...

That's actually great idea! Will definitely try that. I didn't though about this because of jsx like syntax which would require transpilation and that is part I'm struggling with in...

👍 setup is still rough, but thanks for pushing forward 😄 once I will fix small issues with loading I will push it to [blaze-elements](https://github.com/wc-catalogue/blaze-elements) thanks!

sorry for late answer. Well it's kind of hard to get webpack and wct to work together so nothing related to bore. I you are interested I have made it...

cool! yeah that's setup I have started with but the problem is dev experience with that approach, it's ok for CI but for building component library it's straight way to...

I have created simple HELM chart for prometheus remote_read with extensive documentation on how to get all necessary details from Grafana Cloud. Enjoy 😉 https://github.com/Container-Driven-Development/Grafana-Cloud-Proxy

Well it depends on how it will work, if there will be more logic than current skatejs/emit it's more like simulation than raw emit/dispatch For instance according to my findings...

It would be great if I can switch between contexts from anywhere without need to go to list of contexts first, e.g. popup selector when clicking on context name? Also...

> > Also regarding switching, now seems that app will not open same view ( eg. same pod detail ) as last opened, so IMHO context switching is bit more...