[Backlogmanager] [FIWARE-JIRA] (HELP-16568) [fiware-stackoverflow] How to query all services (groups) from an iotagent

[Fernando Lopez (JIRA)]

     [ https://jira.fiware.org/browse/HELP-16568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez reassigned HELP-16568:
-------------------------------------

    Assignee: Roberto Castillo  (was: Jose Gato Luis)

> [fiware-stackoverflow] How to query all services (groups) from an iotagent
> --------------------------------------------------------------------------
>
>                 Key: HELP-16568
>                 URL: https://jira.fiware.org/browse/HELP-16568
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Roberto Castillo
>              Labels: fiware
>
> Created question in FIWARE Q/A platform on 27-02-2020 at 16:02
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/60436577/how-to-query-all-services-groups-from-an-iotagent
> +Question:+
> How to query all services (groups) from an iotagent
> +Description:+
> We have a hard time understanding the meaning of the different hierarchy levels provided by the iotagent. There is the fiware-service, the fiware-servicepath and underneath it is a bunch of services that in turn have a bunch of devices associated.
> Now we understood how to query for all devices and all services underneath a given fiware-service and fiware-servicepath. We also understood how to query for all fiware-servicepaths given a certain fiware-service. But how to query for all those "top level" fiware-services?
> Our goal is to create a device management user interface which enables an end user to provision and unprovision the devices he is managing. Maybe we have a misconception of the fiware-service here but since one can add such services with a certain POST request our expectation would be that we can somehow query for all those services. What are we missing?



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)