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

create database migration service (container) #436

Open
Tracked by #438
josefaidt opened this issue Apr 8, 2023 · 0 comments
Open
Tracked by #438

create database migration service (container) #436

josefaidt opened this issue Apr 8, 2023 · 0 comments
Labels
area: infra Issue pertains to infrastructure (CDK) project: fissure type: feature-request New feature or request

Comments

@josefaidt
Copy link
Contributor

Describe the Feature

As the bot and frontend are split into separate apps, it makes sense to extract the database init and migrations into their own service. This service should:

  • start with project deployment
  • run prisma seed (if necessary, this will create the initial dataset such as ACCESS_LEVELS, etc.)
  • run prisma migrations
  • stop and shutdown

Note: we will need to ensure the bot and frontend services are not impacted by the migrations or seeds run by the (somewhat ephemeral) database service

@josefaidt josefaidt added needs: triage type: feature-request New feature or request area: infra Issue pertains to infrastructure (CDK) project: fissure and removed needs: triage labels Apr 8, 2023
This was referenced Apr 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: infra Issue pertains to infrastructure (CDK) project: fissure type: feature-request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant