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

Add option to read configuration map from database rather than from file #4150

rbeckman-nextgen opened this issue May 11, 2020 · 1 comment


Copy link

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

  • When configurationmap.location is absent or set to "file", same behavior as before, will store in a file specified by configurationmap.path
  • When configurationmap.location is set to "database", it will be stored in the configuration table instead
  • The configuration map is included in the XML file when doing a server config export
    ** This should work whether "file" or "database" is used
  • When restoring the server config, the user is prompted and can choose whether or not to overwrite the configuration map
    ** This should work whether "file" or "database" is used
  • The API route for setting the server config should include a new parameter that determines whether or not the config map will be overwritten

Imported Issue. Original Details:
Jira Issue Key: MIRTH-4274
Reporter: narupley
Created: 2018-05-25T13:01:37.000-0700

@rbeckman-nextgen rbeckman-nextgen added this to the 3.6.0 milestone May 11, 2020
Copy link
Collaborator Author

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

Looking forward to this new feature. Is there an existing migration for moving from the file to database store? Or do all the mappings need to be readded manually post upgrade? I made the change in /conf/ and now my configuration map is empty. As well, the file ${dir.appdata}/ remains.

Imported Comment. Original Details:
Author: kevinfosterng
Created: 2018-07-05T11:15:26.000-0700

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant