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

Support HTTP request for outbound mappings #303

Open
zhongys-c8y opened this issue Jan 23, 2025 · 2 comments
Open

Support HTTP request for outbound mappings #303

zhongys-c8y opened this issue Jan 23, 2025 · 2 comments
Labels
enhancement New feature or request

Comments

@zhongys-c8y
Copy link

Now dynamic mapper support HTTP requests only for inbound mappings. If the dynamic mapper can send requests to another Microservice, the payload can be further processed.

@switschel
Copy link
Collaborator

Doable!
We might need to extend the existing Http Connector to be configured with a Base URL + Authentication.
When a outbound mapping is defined and a HTTP connector is selected the Base URL will be fetched and the mappings topic extended to it e.g. topic /measurements --> https://myOtherMicroservice/api/data/measurments. Payload will be the mapped payload.

Can we make the following assumptions?

  • Can we assume that we always POST data or should we also allow PUT/PATCH methods?
  • Can we assume that the content-type is always application/json for now? Could be a current limitation that it is only supported for JSON payloads, which makes it much easier for us.

@switschel switschel added the enhancement New feature or request label Jan 30, 2025
@zhongys-c8y
Copy link
Author

For the current use case(the payload needs to be decoded), I think POST is already sufficient. Application/json should be also fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants