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

[SPIKE] Define/describe a migration plan/model for the dashboard #12

Open
jchartrand opened this issue Feb 2, 2024 · 0 comments
Open
Labels
minor question Further information is requested

Comments

@jchartrand
Copy link
Contributor

Plan how migrations would work, i.e, how issuers deploying this should upgrade as new code is added.

And specifically with the DB, Payload introduced database migrations in version 2 I think, whereas the admin dashboard uses version 1, so managing database migrations needs to be thought through.

This is another compelling reason to move data CRUD to a restful service (see #9 and #10). Changes would be made by defining a new version of the API, providing a clearer and more consistent contractual definition of change, and allowing implementations to fulfill their side of the contract as best matches their implementation.

@kayaelle kayaelle moved this to Admin Dashboard Backlog in DCC Engineering Feb 7, 2024
@alexfigtree alexfigtree added the question Further information is requested label May 2, 2024
@alexfigtree alexfigtree changed the title Define/describe a migration plan/model for the dashboard [SPIKE] Define/describe a migration plan/model for the dashboard May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
minor question Further information is requested
Projects
Status: Admin Dashboard Backlog
Development

No branches or pull requests

2 participants