This repository has been archived by the owner on Dec 19, 2022. It is now read-only.
fix: use new port assignments (#65), standardise service name (#66) #67
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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-grove-c/blob/master/.github/CONTRIBUTING.md
What is the current behavior?
Issue Number: #65 #66
What is the new behavior?
New port assignments (598xx, 599xx)
Service name is
device-grove
Does this PR introduce a breaking change?
Reconfiguration required for clients using old port numbers
New Imports
Specific Instructions
Scripting in
test/
directory still harbors old port numbers; however this needs to be reworked in any case as export-client is no longer supportedOther information