-
Notifications
You must be signed in to change notification settings - Fork 57
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
refactor: Update for new service key names and overrides for hyphen to underscore #208
refactor: Update for new service key names and overrides for hyphen to underscore #208
Conversation
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
225b20e
to
5ed0bc6
Compare
…o underscore closes #207 closes #189 BREAKING CHANGE: Service key names used in configuration have changed. Signed-off-by: lenny <[email protected]>
5ed0bc6
to
f085b26
Compare
Signed-off-by: lenny <[email protected]>
Is there any way to re-trigger the sdk build? |
@hahattan Yes, DevOps can do it. Once the CI Pipeline issue is resolved, I'll ping them to restart the SDK merge job so I have the tag to use in these DS PRs. Those tag updates will triggers these PRs to build. |
Signed-off-by: lenny <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #208 +/- ##
=======================================
Coverage 55.73% 55.73%
=======================================
Files 13 13
Lines 811 811
=======================================
Hits 452 452
Misses 311 311
Partials 48 48 Continue to review full report at Codecov.
|
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
Dependent on edgexfoundry/go-mod-core-contracts#613
Dependent on edgexfoundry/go-mod-bootstrap#216
Dependent on edgexfoundry/device-sdk-go#926
PR Checklist
Please check if your PR fulfills the following requirements:
If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/device-virtual-go/blob/master/.github/CONTRIBUTING.md
What is the current behavior?
Service key constants have the edgex- prefix
Issue Number: #207 & #189
What is the new behavior?
Service key constants no longer have the edgex- prefix
Hyphen in Overrides are converted to underscore
Does this PR introduce a breaking change?
BREAKING CHANGE: Service key names used in configuration have changed.
New Imports
Specific Instructions
Other information