-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
refactor: Clean up lms/envs/production.py cruft #36115
refactor: Clean up lms/envs/production.py cruft #36115
Conversation
This setting can be overridden in the YAML or derived from a setting that can change based on the YAML so it should be loaded explicitly using _YAML_TOKENS
be14a8f
to
6c24675
Compare
@kdmccormick: Thanks for continuing to clean up the platform! |
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
2U Release Notice: This PR has been deployed to the edX production environment. |
1 similar comment
2U Release Notice: This PR has been deployed to the edX production environment. |
2U Release Notice: This PR has been rolled back from the edX production environment. |
1 similar comment
2U Release Notice: This PR has been rolled back from the edX production environment. |
2U Release Notice: This PR has been deployed to the edX production environment. |
1 similar comment
2U Release Notice: This PR has been deployed to the edX production environment. |
Description
This is a pure refactoring of lms/envs/production.py, removing several redundant statements that have accrued over the years as the platform moved from python-only, to python+json, to python+json+yaml, to today's python+yaml setup.
Notes on some of the more involved refactorings:
lms/envs/common.py is empty. So the update is a no-op and is the same as just loading this data directly from the YAML config.
the individual values is not necessary.
dashboard
djangoapp and can probably be deleted but might be used by plugins so not removing for now to keep the change backward compatible.Testing Instructions
We confirmed that the django settings exposed by lms/envs/production.py were identical using: https://gist.github.com/kdmccormick/9dd58fca319a6372776cd47d9136ffd3
git checkout kdmccormick/lms-envs-production-cleanup git restore upstream/master -s lms/envs/production.py mv lms/envs/production.py lms/envs/production_old.py git restore lms/envs/production.py ./diff_settings.sh lms/envs/production_old.py lms/envs/production.py # should yield a small diff of just random values