Implement new bindings component for Huawei OBS#1724
Conversation
Signed-off-by: jasonlica <[email protected]>
Signed-off-by: jasonlica <[email protected]>
Signed-off-by: Bernd Verst <[email protected]>
|
We need to check why the FOSSA license check is failing before we can merge this PR. I did see that the upstream library is Apache 2.0 so it should not be a concern. |
berndverst
added
do-not-merge
|
@jasonlica please open the documentation PR for this component and link that PR here. We will only merge this PR after the documentation PR has been opened. Thanks! |
@berndverst sure, I will create the documentation PR for this component. thanks. |
|
@jasonlica can you please also address the conflict in the |
@berndverst resolved the conflict. please review, thanks. |
Signed-off-by: Bernd Verst <[email protected]>
@berndverst I have created documentation for this component and linked the PR in the above description. thanks. |
Codecov Report
@@ Coverage Diff @@
## master #1724 +/- ##
==========================================
+ Coverage 36.37% 36.75% +0.38%
==========================================
Files 166 176 +10
Lines 15488 15930 +442
==========================================
+ Hits 5633 5855 +222
- Misses 9228 9419 +191
- Partials 627 656 +29
Continue to review full report at Codecov.
|
|
Thanks for your contribution @jasonlica |
berndverst
removed
do-not-merge
@berndverst it is our pleasure! thanks to the community. |
2 participants
Description
Huawei OBS is implemented as an output bindings component into the Dapr. This can be a counterpart to the existing AWS S3 bindings component.
Object Storage Service (OBS) provides stable, secure, efficient, and easy-to-use cloud storage that lets you store virtually any volume of unstructured data in any format and access it from anywhere using REST APIs.
See Huawei OBS User Guide for reference.
I will provide the documentation for this component usage later and will raise a PR for that when the PR for this component is being approved.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #1718
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: