datamaintain
datamaintain copied to clipboard
One tool to maintain all your database schemas!
See #90 Option to save logs on the filesystem. There will be one log file by script executed during the Datamaintain execution.
The properties read by Datamaintain have no prefix currently. For example, the one used to read the db uri is `db.uri`. It may cause problems if the user's application has...
**Currently:** The `mongo-shell` option is only available in the subcommand `update-db`. The two other commands, `list` and `mark-one-script-as-executed` can't use a specified mongo shell, they only use the default shell,...
Verbose and trace (verbose ++) are a logger level, now every class can use it. Some log are modify, like normal mode print less (no config, summary print only executed...
* accepting multiple options * accepting multiple hosts * throwing precise errors
This module should contain: - AppSubProcessUtils.kt - Builders utils (DatamaintainConfig builder for example) - FakeDriver Be careful: there is a need to extract domain objects from core to another module...
Currently, verbose and logger in general are lock in DatamaintainConfig (in context). The context class is not accessible from driver class (or other). We need to allow it, maybe by...
Before 3.0, the packages used are `datamaintain/datamaintain`. Switch to only `datamaintain` on branch dev. The only to do is remove "datamaintain" in the workflow file (`.github/workflows/publish_docker_packages.yaml`). This issue is just...
Currently, the GitHub workflow that publishes Docker images releases all Mongo versions sequentially. This is quite slow and could be improved by running them all in parallel. This can be...
When releasing a version, only amd images are created. There are more and more computers with ARM chips, it would be nice to have packages for both