Skip to content
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

migration for surpassed deep future date #79

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

pbugni
Copy link

@pbugni pbugni commented Feb 5, 2025

@pbugni pbugni requested review from mcjustin and ivan-c February 5, 2025 22:28
Comment on lines +2 to +3
revision = '7542b481-21cb-483c-b72a-6c1502375a65'
down_revision = '17f3b60d-0777-4d0e-bb32-82e670b573a7'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious, where do you get these values from?

Copy link
Author

@pbugni pbugni Feb 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are UUIDs, built into the FHIR Migrations framework.
The most recent migration run is stored in a FHIR Basic object. To generate these automatically, run the following:
dc exec <service> flask migrate <name-of-migration-script-to-generate>

For example, I ran:
dc exec messagingservice flask migrate patch_DEEP_FUTURE_last_unfollowedup

and as it found the down_revision in the DB, fabricated a shell script in migrations/version/<name>.py which included those and boiler plate functions to extend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants