🤖 Add skip_db option for conditional database initialization #1611
+10
−5
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.
👋 Hi there! This PR was automatically generated by Autofix 🤖
This fix was triggered by Jenn Mueng
Fixes SEER-9P
This change introduces a new parameter 'skip_db' to the 'bootup' function in 'src/seer/bootup.py' to allow skipping the database initialization process. If 'skip_db' is set to True, the 'initialize_database' function will not be called. This enables better control over the bootup sequence, especially for scenarios where database initialization is not required. Additionally, in 'src/celery_app/app.py', the function 'initialize_celery_database' is called before booting up to ensure proper integration with Celery's configuration.
If you have any questions or feedback for the Sentry team about this fix, please email [email protected] with the Run ID: 2145.