Lfx cleanup#44
Merged
Merged
Conversation
theyoyojo
approved these changes
Mar 25, 2024
theyoyojo
left a comment
Contributor
There was a problem hiding this comment.
tbh this could have been a single commit but it's all good
Since we are moving away from this system of sharing resources a good place to start is to provide a default of false for lfx so that more places can avoid refering to it.
To make the query simpler, since lfx was always being set to 0 (False) and the default is false, it does not need to be specified.
since 326c3d6 ("orbit: remove cruft related to lfx from mail_auth") we have not needed this database query.
since we are no longer querying the LFX status of students as part of the mail auth flow, the ability to change LFX status with the -x and -y options in hyperspace are uneeded.
since the -x and -y options are no longer calling these functions, they are unused.
Since there are no callers for these functions, they (and their associated queries) are no longer needed
since lfx is always false and can no longer be printed, it does not need to be displayed when viewing the student roster.
Since there are no references to the lfx field, it does not need to be stored.
Contributor
|
PASS: |
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
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.
Since we have found a solution for running more than one independent version of the infrastructure, we no longer need to support lfx/non lfx for the mail servers. Since 326c3d6 we have not done so, but the lfx field remains in the database and in several queries. This PR removes all references to it.