feat: dump_settings management command - #36162
Merged
kdmccormick merged 1 commit intoJan 27, 2025
Merged
Conversation
kdmccormick
force-pushed
the
kdmccormick/dump-settings
branch
3 times, most recently
from
January 24, 2025 17:08
6c7900c to
c1fb2ea
Compare
kdmccormick
marked this pull request as ready for review
January 24, 2025 17:09
Member
Author
|
Need to handle the DisableMigrations object: |
1 task
kdmccormick
force-pushed
the
kdmccormick/dump-settings
branch
5 times, most recently
from
January 27, 2025 18:58
e88c7e3 to
1c3eab9
Compare
kdmccormick
force-pushed
the
kdmccormick/dump-settings
branch
from
January 27, 2025 19:08
1c3eab9 to
3e961cb
Compare
This command dumps the current Django settings to JSON for debugging/diagnostics. The output of this command is for *humans*... it is NOT suitable for consumption by production systems. In particular, we are introducing this command as part of a series of refactorings to the Django settings files lms/envs/* and cms/envs/*. We want to ensure that these refactorings do not introduce any unexpected breaking changes, so the dump_settings command will both help us manually verify our refactorings and help operators verify that our refactorings behave expectedly when using their custom python/yaml settings files. Related to: openedx#36131
kdmccormick
force-pushed
the
kdmccormick/dump-settings
branch
from
January 27, 2025 19:10
3e961cb to
0aed33b
Compare
Contributor
|
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
Contributor
|
2U Release Notice: This PR has been deployed to the edX production environment. |
leoaulasneo98
pushed a commit
to aulasneo/edx-platform
that referenced
this pull request
Jan 30, 2025
This command dumps the current Django settings to JSON for debugging/diagnostics. The output of this command is for *humans*... it is NOT suitable for consumption by production systems. In particular, we are introducing this command as part of a series of refactorings to the Django settings files lms/envs/* and cms/envs/*. We want to ensure that these refactorings do not introduce any unexpected breaking changes, so the dump_settings command will both help us manually verify our refactorings and help operators verify that our refactorings behave expectedly when using their custom python/yaml settings files. Related to: openedx#36131
jciasenza
pushed a commit
to jciasenza/edx-platform
that referenced
this pull request
Feb 25, 2025
This command dumps the current Django settings to JSON for debugging/diagnostics. The output of this command is for *humans*... it is NOT suitable for consumption by production systems. In particular, we are introducing this command as part of a series of refactorings to the Django settings files lms/envs/* and cms/envs/*. We want to ensure that these refactorings do not introduce any unexpected breaking changes, so the dump_settings command will both help us manually verify our refactorings and help operators verify that our refactorings behave expectedly when using their custom python/yaml settings files. Related to: openedx#36131
UsamaSadiq
pushed a commit
that referenced
this pull request
May 14, 2025
This command dumps the current Django settings to JSON for debugging/diagnostics. The output of this command is for *humans*... it is NOT suitable for consumption by production systems. In particular, we are introducing this command as part of a series of refactorings to the Django settings files lms/envs/* and cms/envs/*. We want to ensure that these refactorings do not introduce any unexpected breaking changes, so the dump_settings command will both help us manually verify our refactorings and help operators verify that our refactorings behave expectedly when using their custom python/yaml settings files. Related to: #36131
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.
Description
This command dumps the current Django settings to JSON for
debugging/diagnostics. The output of this command is for humans... it
is NOT suitable for consumption by production systems.
In particular, we are introducing this command as part of a series of
refactorings to the Django settings files lms/envs/* and cms/envs/*.
We want to ensure that these refactorings do not introduce any
unexpected breaking changes, so the dump_settings command will both help
us manually verify our refactorings and help operators verify that our
refactorings behave expectedly when using their custom python/yaml
settings files.
Supporting info
Example output: https://gist.github.com/kdmccormick/f13d087679ca6c3ba067f03bf58b7aa1
Related to: #36131