fix(DATAGO-125814): implement lazy imports to improve CLI startup performance#1087
Open
fix(DATAGO-125814): implement lazy imports to improve CLI startup performance#1087
Conversation
…_validate_database function
solace-mdupls
approved these changes
Feb 27, 2026
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.
What is the purpose of this change?
This change improves the CLI startup performance by implementing lazy imports, ensuring that heavy dependencies like Flask and SQLAlchemy are only loaded when actually needed rather than at startup time.
How was this change implemented?
Key Design Decisions
Lazy importing was chosen as a lightweight solution to improve CLI responsiveness without restructuring the codebase. This approach provides immediate performance benefits while maintaining backward compatibility and requiring minimal code changes.
How was this change tested?
Is there anything the reviewers should focus on/be aware of?
Reviewers should check that error handling is appropriate when imports fail at runtime rather than startup.