heisenbergs-uncertainty opened a new pull request, #3541:
URL: https://github.com/apache/streampipes/pull/3541
…functionality, and more extensive logging.
<!--
~ Licensed to the Apache Software Foundation (ASF) under one or more
~ contributor license agreements. See the NOTICE file distributed with
~ this work for additional information regarding copyright ownership.
~ The ASF licenses this file to You under the Apache License, Version 2.0
~ (the "License"); you may not use this file except in compliance with
~ the License. You may obtain a copy of the License at
~
~ http://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing, software
~ distributed under the License is distributed on an "AS IS" BASIS,
~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~ See the License for the specific language governing permissions and
~ limitations under the License.
~
-->
<!--
Thanks for contributing! Here are some tips you can follow to help us
incorporate your contribution quickly and easily:
1. If this is your first time, please read our contributor guidelines:
- https://streampipes.apache.org/community/get-involved/
- https://cwiki.apache.org/confluence/display/STREAMPIPES/Getting+Started
2. Make sure the PR title is formatted like: `[#<GitHub issue id>] PR title
...`
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
`[WIP][#<GitHub issue id>] PR title ...`.
4. Please write your PR title to summarize what this PR proposes/fixes.
5. Link the PR to the corresponding GitHub issue (if present) in the
`Development` section in the right menu bar.
6. Be sure to keep the PR description updated to reflect all changes.
7. If possible, provide a concise example to reproduce the issue for a
faster review.
8. Make sure tests pass via `mvn clean install`.
9. (Optional) If the contribution is large, please file an Apache ICLA
- http://apache.org/licenses/icla.pdf
-->
### Purpose
This enhances the currently implemented RestPublisher Data Sink which has
very little functionality outside of making a request. Many implementations of
REST functionality are going to be utilizing the sink to trigger a webhook
which should at bare minimum use authorization to confirm the legitimacy of the
request origin. This enhancement allows for the addition of custom headers so
that more advanced REST scenarios can be addressed with the RestPublisher. I
have also added retry functionality on failure, timeouts, and better logging
for more advanced debugging.
This also upgrades the interfaces on from older streampipes models to the
newer "IDataSinkInterface" as demonstrated by the Streampipes tutorial
documentation.
Here is a picture of what the new sink looks like in the UI:
<img width="1632" alt="image"
src="https://github.com/user-attachments/assets/7ed0a12c-310e-40ef-9ec0-0d9b8564befe";
/>
Here is an example of this same request hitting RequestBin:
<img width="525" alt="image"
src="https://github.com/user-attachments/assets/478bf76b-10d4-4dec-a645-4026b90e2270";
/>
### Remarks
No remarks.
PR introduces (a) breaking change(s): no
PR introduces (a) deprecation(s): no
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
