Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mentioned service path isn't the same as Orion's #762

Merged
merged 1 commit into from
Jun 14, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions RELEASE_NOTES.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@
- Fix to return OK/200 and an empty result set when no data found (#720)
- Fix to return id and type in place of entityId and entityType (#751)
- Fixed failing test cases of test_geocoding.py (#755)
- Mentioned service path isn't the same as Orion's (#758)

### Important: Backward compatibility

Expand Down
5 changes: 4 additions & 1 deletion docs/manuals/user/using.md
Original file line number Diff line number Diff line change
Expand Up @@ -448,7 +448,10 @@ Use the filters to delete only records in certain intervals of time.

QuantumLeap supports the use of different tenants, just like Orion does with
the usage FIWARE headers documented
[here](https://fiware-orion.readthedocs.io/en/master/user/multitenancy/index.html).
[here](https://fiware-orion.readthedocs.io/en/master/orion-api.html#multi-tenancy).
However, QuantumLeap does not handles Fiware-ServicePath in queries the same way
Orion does. In QuantumLeap, Fiware-ServicePath used in headers when inserting data
and querying data should be same.

Recall the use of tenancy headers (`Fiware-Service` and `Fiware-ServicePath`) is
optional. Data insertion and retrieval will work by default without those.
Expand Down
8 changes: 5 additions & 3 deletions specification/quantumleap.yml
Original file line number Diff line number Diff line change
Expand Up @@ -156,22 +156,24 @@ parameters:
required: false
type: string
description: "The corresponding 'fiware-service' header.
See http://fiware-orion.readthedocs.io/en/latest/user/multitenancy/index.html#multi-tenancy"
See https://fiware-orion.readthedocs.io/en/master/orion-api.html#multi-tenancy"
fiware-ServicePath:
in: header
name: fiware-ServicePath
required: false
type: string
description: "The corresponding 'fiware-servicepath' header.
See http://fiware-orion.readthedocs.io/en/latest/user/multitenancy/index.html#multi-tenancy"
See https://fiware-orion.readthedocs.io/en/master/orion-api.html#multi-tenancy
However, QuantumLeap does not handles Fiware-ServicePath in queries the same way Orion does.
In QuantumLeap, Fiware-ServicePath used in headers when inserting data and querying data should be same."
fiware-correlator:
in: header
name: Fiware-Correlator
required: false
type: string
description: "The request correlation ID Context Broker forwards in
notification messages.
See https://fiware-orion.readthedocs.io/en/latest/admin/logs/index.html"
See https://fiware-orion.readthedocs.io/en/master/devel/httpHeaders.html#20-fiware-correlator"

################################################################################
# PARAMETERS: IN PATH
Expand Down
Loading