-
Notifications
You must be signed in to change notification settings - Fork 4
feat(CI): added deployment skip, migration automation, and key manager steps #121
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
Open
waterkimchi
wants to merge
15
commits into
main
Choose a base branch
from
ci_enhancements
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
Open
Production deployment not tested |
<!--- Provide a general summary of your changes in the Title above --> ## Description Introduces a new "websocSectionEnrollmentLive" table to the schema, purposed to keep track of updated enrollment data based on continuous scrapes. Updated the websoc scraper to populate new table every 5 minutes. The table holds short term data, clearing out all entries older than an hour every scrape. Added REST endpoint functionality for the new table, which retrieves enrollment snapshots based on a `since` timestamp. - The API returns: - A "from" snapshot representing the latest known state before `since` (if available). - A "to" snapshot representing the latest known state. - If no significant changes are detected, only "to" is returned. ## Related Issue Closes [#59] ## Motivation and Context Allows developers to create accurate applications of UCI's enrollment information, helping student's quarterly enrollment processes go smoother and be more communicative. ## How Has This Been Tested? the schema and scraper were tested across numerous scapes in 5 minute intervals, and the data was validated for consistency. ## Screenshots (if appropriate): ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [X] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Checklist: - [X] My code involves a change to the database schema. - [ ] My code requires a change to the documentation. --------- Co-authored-by: Sanskar Mishra <[email protected]> Co-authored-by: Jordan <[email protected]> Co-authored-by: Jordan Yee <[email protected]> Co-authored-by: Dante Dam <[email protected]> Co-authored-by: Andrew Wang <[email protected]>
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.
Description
Improves the CI pipeline by adding the following enhancements:
no deploy
label on PRs(TODO: set the labels). If present, the staging deployment is skipped.Related Issue
#81
Motivation and Context
no deploy
(TODO: set the labels) label allows contributors to control this.How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: