-
-
Notifications
You must be signed in to change notification settings - Fork 650
Avoid creating duplicated settings files when automigration is disabled #2974
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
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2974 +/- ##
=======================================
Coverage 62.02% 62.03%
=======================================
Files 102 102
Lines 14427 14428 +1
=======================================
+ Hits 8949 8950 +1
Misses 5478 5478
Continue to review full report at Codecov.
|
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.
LGTM. Thanks for the fix. Sorry that I have overlooked this.
@meaksh Could you squash the black commit into your commit where you introduced the changes please? |
d6c38d8
to
cea0f6a
Compare
@SchoolGuy done 👍 |
We introduced a PR #2966 to disable setting automigration to be executed by default, this works fine but we just noticed there are still duplicated settings files being created on each restart of cobbler or during instantiation of
CobblerAPI
object:This PR simply fixed this issue by preventing we save a copy of the settings when automigration was not performed.