Open
Conversation
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
niranjanivivek
force-pushed
the
pr_fe_config_db_journal
branch
from
4a7c62f to
3e52738
Compare
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
@sreeiyer-1, Please review. |
Contributor
Author
ndas7
suggested changes
Feb 3, 2026
niranjanivivek
force-pushed
the
pr_fe_config_db_journal
branch
from
3e52738 to
27b0f0b
Compare
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
niranjanivivek
force-pushed
the
pr_fe_config_db_journal
branch
from
27b0f0b to
07d2881
Compare
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
niranjanivivek
force-pushed
the
pr_fe_config_db_journal
branch
from
07d2881 to
8786339
Compare
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
niranjanivivek
force-pushed
the
pr_fe_config_db_journal
branch
from
8786339 to
5f9018d
Compare
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ndas7
reviewed
Feb 18, 2026
niranjanivivek
force-pushed
the
pr_fe_config_db_journal
branch
from
5f9018d to
752f1d0
Compare
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
niranjanivivek
force-pushed
the
pr_fe_config_db_journal
branch
from
752f1d0 to
5bb3fd6
Compare
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ndas7
reviewed
Mar 7, 2026
niranjanivivek
force-pushed
the
pr_fe_config_db_journal
branch
from
5bb3fd6 to
1425aa7
Compare
Contributor
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
niranjanivivek
force-pushed
the
pr_fe_config_db_journal
branch
from
1425aa7 to
d0ab6cd
Compare
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ndas7
reviewed
Mar 12, 2026
niranjanivivek
force-pushed
the
pr_fe_config_db_journal
branch
from
d0ab6cd to
d57809e
Compare
Contributor
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
niranjanivivek
force-pushed
the
pr_fe_config_db_journal
branch
from
d57809e to
d46ab5c
Compare
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
niranjanivivek
force-pushed
the
pr_fe_config_db_journal
branch
from
d46ab5c to
de3ff9c
Compare
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
niranjanivivek
force-pushed
the
pr_fe_config_db_journal
branch
from
de3ff9c to
8ebe484
Compare
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Niranjani Vivek <niranjaniv@google.com>
niranjanivivek
force-pushed
the
pr_fe_config_db_journal
branch
from
8ebe484 to
66aef68
Compare
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Add ConfigDB Journal Feature. The ConfigDB Journal would capture writes to the database in a file on the switch.
Dependency PR:
Base BE PR to be merged first : Implement RCM - PR#202
UT Test results for Config DB Journal:
=== RUN TestNewDbJournal
=== RUN TestNewDbJournal/Success
=== RUN TestNewDbJournal/InvalidDb
--- PASS: TestNewDbJournal (0.00s)
--- PASS: TestNewDbJournal/Success (0.00s)
--- PASS: TestNewDbJournal/InvalidDb (0.00s)
=== RUN TestDbJournalInit
=== RUN TestDbJournalInit/Success
=== RUN TestDbJournalInit/NilRedisClient
--- PASS: TestDbJournalInit (0.00s)
--- PASS: TestDbJournalInit/Success (0.00s)
--- PASS: TestDbJournalInit/NilRedisClient (0.00s)
=== RUN TestDbJournalUpdateCache
=== RUN TestDbJournalUpdateCache/SuccessHSet
=== RUN TestDbJournalUpdateCache/SuccessDel
=== RUN TestDbJournalUpdateCache/NilCache
=== RUN TestDbJournalUpdateCache/NilRedisClient
--- PASS: TestDbJournalUpdateCache (0.00s)
--- PASS: TestDbJournalUpdateCache/SuccessHSet (0.00s)
--- PASS: TestDbJournalUpdateCache/SuccessDel (0.00s)
--- PASS: TestDbJournalUpdateCache/NilCache (0.00s)
--- PASS: TestDbJournalUpdateCache/NilRedisClient (0.00s)
=== RUN TestDbJournalRotateFile
--- PASS: TestDbJournalRotateFile (3.46s)
=== RUN TestConfigDbJournal
=== RUN TestConfigDbJournal/HSetNew
=== RUN TestConfigDbJournal/HSetExisting
=== RUN TestConfigDbJournal/HDel
=== RUN TestConfigDbJournal/Set
=== RUN TestConfigDbJournal/Del
--- PASS: TestConfigDbJournal (5.90s)
--- PASS: TestConfigDbJournal/HSetNew (0.50s)
--- PASS: TestConfigDbJournal/HSetExisting (0.50s)
--- PASS: TestConfigDbJournal/HDel (0.50s)
--- PASS: TestConfigDbJournal/Set (0.50s)
--- PASS: TestConfigDbJournal/Del (0.50s)
Why I did it
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)