[portmgrd/portsyncd] Refactor code so that portsyncd does not deal with configurations at run time #1085
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.
Refactor code so that portsyncd does not deal with configurations at run time
portmgrd will deal with configurations for both linux side and appDB.
Added vs test cases for port config changes
Signed-off-by: Zhenggen Xu zxu@linkedin.com
What I did
Refactor code so that portsyncd does not deal with configurations at run time
portmgrd will deal with configurations for both linux side and appDB.
Added vs test cases for port config changes
Why I did it
Only one daemon is handling port configurations from cfg_db to app-db/linux.
How I verified it
vs test cases
Details if related
-- Initial configurations is not moved yet.
-- port_config.ini dependencies is not removed yet.