Document behaviour of concurrent confdb accesses#341
Merged
Conversation
miguelpires
force-pushed
the
confdb-concurrent
branch
from
978d799 to
ab9938c
Compare
maykathm
reviewed
May 19, 2026
maykathm
reviewed
May 19, 2026
Signed-off-by: Miguel Pires <miguel.pires@canonical.com>
miguelpires
force-pushed
the
confdb-concurrent
branch
from
ab9938c to
5a23091
Compare
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
2 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.
Documents the behaviour of concurrent confdb accesses in the
snapctlconfdb section and the how-to guide.https://warthogs.atlassian.net/browse/SNAPDENG-35595