Open
Conversation
✅ Deploy Preview for flowfile-wasm canceled.
|
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.
This pull request introduces Alembic-based database migrations to the
flowfile_corepackage, establishing a robust and maintainable schema management process. It adds the initial schema definition with all core tables, configures Alembic environment and templates, and ensures migration files are bundled for runtime access (e.g., with PyInstaller). The build process is updated so that Alembic migration files are included in the packaged application.Database migration infrastructure:
alembic.iniconfiguration,env.pyenvironment script, and a migration script template (script.py.mako) for generating future migration files. [1] [2] [3]001_initial_schema.py) that creates all the core tables needed for the catalog, user management, secrets, connections, scheduling, and artifacts, along with all necessary constraints and relationships.Build and packaging updates:
get_alembic_datas) inmain.pyto collect Alembic migration files and configuration for inclusion in the build output, ensuring migrations are available at runtime (e.g., when using PyInstaller). The build process now includes these files in thedatasparameter of the PyInstallerAnalysis. [1] [2]