-
Notifications
You must be signed in to change notification settings - Fork 407
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
feat: upgrade YurtIoTDock to support edgex v3 api #1666
Conversation
…ersions Signed-off-by: wangxye <[email protected]>
Signed-off-by: wangxye <[email protected]>
SonarCloud Quality Gate failed. 0 Bugs No Coverage information Catch issues before they fail your Quality Gate with our IDE extension SonarLint |
Codecov Report
@@ Coverage Diff @@
## master #1666 +/- ##
==========================================
+ Coverage 52.32% 53.03% +0.70%
==========================================
Files 154 158 +4
Lines 17637 18504 +867
==========================================
+ Hits 9228 9813 +585
- Misses 7582 7796 +214
- Partials 827 895 +68
Flags with carried forward coverage won't be shown. Click here to find out more.
|
/assign @LavenderQAQ @Rui-Gan |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
@LavenderQAQ: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LavenderQAQ, rambohe-ch, wangxye The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/sig iot
/kind feature
/kind bug
What this PR does / why we need it:
Upgrade the api to keep up with the new version of edgex v3.
Which issue(s) this PR fixes:
Fixes #1615 and #1627
Does this PR introduce a user-facing change?