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

filemanager: reconsider the CdkResourceInvoke for migration #170

Closed
mmalenic opened this issue Mar 18, 2024 · 0 comments · Fixed by #213
Closed

filemanager: reconsider the CdkResourceInvoke for migration #170

mmalenic opened this issue Mar 18, 2024 · 0 comments · Fixed by #213
Labels
feature New feature filemanager an issue relating to the filemanager

Comments

@mmalenic
Copy link
Member

Currently the CdkResourceInvoke construct only performs database initialization, and does not retrigger when a new migration is required. It also does not fail the CDK stack if a migration fails.

To address this, instead of a SingletonLambda, a proper Lambda function should be used to allow retriggering. The Provider construct could also be used to perform database migration while CDK is deploying, however it should also be possible to manually trigger a migration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature New feature filemanager an issue relating to the filemanager
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: provider construct and filemanager migration umccr/orcabus
1 participant
@mmalenic