zestones — gestern um 09:50 Uhr Hi, I am trying to browse the topics with the graphql API but I only get an empty list as a result even though i see my topics being published in the topic browser (in the management console). I also properly mapped the port when launching the umh-core instance with docker, so i have access to the graphql port : services: umh-core: image: management.umh.app/oci/united-manufacturing-hub/umh-core:v0.43.9 container_name: umh-core restart: unless-stopped ports: - "8090:8090" When I try the curl command present in the documentation : curl -X POST http://localhost:8090/graphql -H "Content-Type: application/json" -d '{"query": "{ topics(limit: 10) { topic } }"}' I get empty topic list : {"data":{"topics":[]}} maybe I missed something, does anyone have any idea on what could be happening ? Bild Bild Brian Pribe — gestern um 14:36 Uhr I think it’s only for current state too when I read the docs zestones — gestern um 14:41 Uhr yes it is for current state, that's why i was expecting to see the published topics in "real time" similar to the topic browser in the management console. But I never get anything returned, even though topics are being published (1 per second), I expected to at least see the current topic Jermuk — gestern um 18:43 Uhr let me look into that (posting it into umh-support would have been better next time 🙂 )

thanks 🙏

hi 🙂 as i am pretty new to umh and as i've got a lot of topics at once on me right now rest assured i will look at this as soon as i find time but it will likely be a few weeks i will not forget it, promised

Hi, no worries I understand that it is not a top priority, thx again for your support

Hi, I got the same issue. Are there any news already?

so far we have not decided to bring it back on our roadmap. it was an experiment to see if people woudl like to see it (and for some reason it broke, but it is fine as it was experiment anyway and marked as such), we are now incorproating it into the overall roadmap for Q3 when we will provide a proper UMH API (where one can then put a I3X wrapper on top of it if one wants, but making the data available for the APi is the msot difficult part)

sounds great, is it also planned to implement pushing data into UMH using the new API?

yes! but this one you can already do now ( a lot of people in our VE team are doign it like this). create a bridge or standalone with http_server as input and uns as output. then in front of the http server, put a reverse proxy for enterprise requirements https://docs.umh.app/production/deployment/docker-compose/advanced/nginx