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.

Sign up for GitHub

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

Jump to bottom

Detect if migrations digest has changed to trigger db recreation in ftl dev #4041

Open
matt2e opened this issue Jan 15, 2025 · 1 comment
Open

Detect if migrations digest has changed to trigger db recreation in ftl dev #4041

matt2e opened this issue Jan 15, 2025 · 1 comment
Labels
next Work that will be be picked up next

Comments

@matt2e
Copy link
Collaborator

matt2e commented Jan 15, 2025

Currently if a db migration file is modified during development, the db does not match the new migration file. You have to stop ftl dev and re-run it with ftl dev --recreate
@github-actions github-actions bot added the triage Issue needs triaging label Jan 15, 2025
@alecthomas alecthomas mentioned this issue Jan 15, 2025
Open
@matt2e matt2e mentioned this issue Jan 20, 2025
Open
@alecthomas alecthomas added the next Work that will be be picked up next label Jan 27, 2025
@github-actions github-actions bot removed the triage Issue needs triaging label Jan 27, 2025
@alecthomas
Copy link
Collaborator

We think we need (just in dev):

  • Nuke resources on schema change - database, topic, etc.
  • Fixtures

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
next Work that will be be picked up next
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alecthomas @matt2e