[DPE-3493] stop snap from sending undesireable updates to pbm config
#42
Conversation
This file contains 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
MiaAltieri
force-pushed
the
test-new-pbm
branch
from
66ea215
to
526e151
Compare
dmitry-ratushnyy
approved these changes
Feb 7, 2024
MiaAltieri
force-pushed
the
test-new-pbm
branch
from
526e151
to
8951fdb
Compare
Mehdi-Bendriss
approved these changes
Feb 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue
When the URI is updated the snap updates
pbm configwith an empty file. Ifmongodis running as a shard this effectively wipes the entire cluster configSolution
Remove the call to wipe config
$SNAP/usr/bin/pbm" config --file "${PBM_CONFIG_FILE}";Other
Remove the addition of
--setParameter processUmask=037 \to the mongod start args, this should be done inside the charm