You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Kevan Jahanshahi (Jira)" <ji...@apache.org> on 2022/08/12 09:45:00 UTC
[jira] [Assigned] (UNOMI-622) Improve migration system to support automation
[ https://issues.apache.org/jira/browse/UNOMI-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevan Jahanshahi reassigned UNOMI-622:
--------------------------------------
Assignee: Kevan Jahanshahi
> Improve migration system to support automation
> ----------------------------------------------
>
> Key: UNOMI-622
> URL: https://issues.apache.org/jira/browse/UNOMI-622
> Project: Apache Unomi
> Issue Type: Improvement
> Reporter: romain.gauthier
> Assignee: Kevan Jahanshahi
> Priority: Major
>
> The idea is about adding a new env variable like the one we have for autoStart:
> unomi.autoStart: true
> We would introduce a new one:
> unomi.autoMigrate: 1.6.0.
> This new env variable would be catched by the same code as the first one and will call migration cmd with the passed version.
> Not that:
> * we may have to fail in case of migration config is not provided, because for automation it's mandatory to have the migration config.
> * We will have to test this on the docker image to insure it's working correctly
> * About dockering we may have to map existing migration cfg file with env variable, it's not currently the case.
> The expected flow of a migration automated should be:
> * stop running Unomi 1.6.x
> * keep ES started
> * start docker container unomi 2.0.0 with env settings:
> ** autoMigrate: 1.6.0
> ** + migrate conf envs
> ** autoStart: true
> At the end the started Unomi should be migrated and started correctly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)