-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add new Redis database PROFILE_DB #11781
base: master
Are you sure you want to change the base?
Conversation
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Commenter does not have sufficient privileges for PR 11781 in repo sonic-net/sonic-buildimage |
Close and re-open to bypass this issue: |
/azp run Azure.sonic-buildimage |
Commenter does not have sufficient privileges for PR 11781 in repo sonic-net/sonic-buildimage |
@@ -93,6 +93,11 @@ | |||
"id" : 14, | |||
"separator": ":", | |||
"instance" : "redis" | |||
}, | |||
"PROFILE_DB" : { | |||
"id" : 15, |
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.
This id will conflict with TEST_DB.
Add new Redis database PROFILE_DB
Why I did it
Add new PROFILE_DB so profile in J2 template will render to this DB.
Also, swss-common will change to read profile from this new DB.
This will simplify reboot handling logic.
How I did it
Add PROFILE_DB config in database_config.j2 and database_config.json.
How to verify it
Pass all E2E test case.
Which release branch to backport (provide reason below if selected)
Description for the changelog
Add new Redis database PROFILE_DB
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)