Closed fbuedding closed 8 months ago
This is actually a docu-bug. That capability has not been ever available in IOTA APIs and the documentation is wrong mentioning it. PR #1556 fixes the documentation.
The ability to query base in service path wildcards belong to Orion Context Broker. Have a look to this section of the documentation: https://github.com/telefonicaid/fiware-orion/blob/master/doc/manuals/orion-api.md#service-path (btw, the wilcard is #
and not *
...).
Thanks for raising this!
The ability to query base in service path wildcards belong to Orion Context Broker. Have a look to this section of the documentation: https://github.com/telefonicaid/fiware-orion/blob/master/doc/manuals/orion-api.md#service-path (btw, the wilcard is
#
and not*
...).
Ah okay thanks! One last question: querying Configs Groups with /*
works, will this get removed then?
querying Configs Groups with
/*
works, will this get removed then?
Strictly speaking, we have not removed it, as you cannot remove something that never has been there ;)
More precise would be to say: querying query Config Groups with /*
is not within the IOTAs functionality.
IoT Agent Node Lib version the issue has been seen with
3.3.0
Bound or port used (API interaction)
Northbound (Provision API and NGSI Interactions)
NGSI version
NGSIv2
Are you running a container?
Yes, I am using a contaner (Docker, Kubernetes...)
Image type
normal
Expected behaviour you didn't see
When listing devices with FIWARE ServicePath wildcard, documented here, all devices under the FIWARE service should be returned.
Unexpected behaviour you saw
A response with status code 200 is returned, but with empty device list.
Steps to reproduce the problem
Repsonse:
Configs
Log output