-
Notifications
You must be signed in to change notification settings - Fork 0
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
Deploying with SEED= wipes out existing projects #573
Comments
@ksuruli said in slack:
TODO: Try to reproduce |
I can not reproduce this error in
|
Trying the |
@ychae @jaeddy I can not reproduce this issue either in @ychae If you still have this issue, please fill in a complete bug report with version of the code used, commands executed, output of the logs, etc. |
@tschaffter Thanks for the detailed update -- I think for this we'll have to schedule a call with you and @ksuruli (and also possible @Pawel-Madej) to work through this together. I'll ping you on Slack to see if I can get some time slots for this session. UPDATE: meeting scheduled for Thursday Oct 17 @ 9:30am |
@ychae This will be addressed by Roche/GNE when they will migrate data from their alpha4 DB to the current version of the portal. Removing from Milestone 2 as this is not an issue with the current version of the codebase. |
When deploying production with the seed set to blank or
default
it wipes out all existing mongo db content. However, if you try to add a new data catalog from before that has a same name, it gives a duplicate key error (see ticket #572)The text was updated successfully, but these errors were encountered: