Add EdgeDBManager for provider-specific database migrations #61155
Conversation
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
Implement EdgeDBManager to integrate Edge3 provider with Airflow's external database manager system, enabling independent schema version control for Edge3 tables separate from core Airflow migrations. This enables Edge3 provider to manage its database schema evolution independently from core Airflow, allowing for provider-specific version control and migration management. The infrastructure is ready for use once initial migration files are generated and the legacy _check_db_schema() approach in EdgeExecutor.start() is removed.
boring-cyborg
bot
added
area:providers
provider:edge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Implement EdgeDBManager to integrate Edge3 provider with Airflow's
external database manager system, enabling independent schema version
control for Edge3 tables separate from core Airflow migrations.
This enables Edge3 provider to manage its database schema evolution
independently from core Airflow, allowing for provider-specific version
control and migration management. The infrastructure is ready for use
once initial migration files are generated and the legacy _check_db_schema()
approach in EdgeExecutor.start() is removed.
With this we should now be able to user airflow db framework to reset.
Alternate approach to #60752 keeping changes local to edge3 provider
Reference: https://github.com/ephraimbuddy/ticketing
Was generative AI tooling used to co-author this PR?
Claude Code