You can supply a config with a task key whose value is a map that identifies a task and any arguments it needs. The task is then dispatched on id with a connection and any arguments supplied. A task config will not run the http server or consensus, though that will need to be revisited once we add back support for raft consensus.
The sid migration takes a list of ledger aliases and migrates them one at a time.
There is an example task config in the resources directory.
You would run the sid migration by starting server like this:
<regular jar invocation start> -p task -c <path-to-task-config>
This introduces the concept of a task.
You can supply a config with a task key whose value is a map that identifies a task and any arguments it needs. The task is then dispatched on id with a connection and any arguments supplied. A task config will not run the http server or consensus, though that will need to be revisited once we add back support for raft consensus.
The sid migration takes a list of ledger aliases and migrates them one at a time.
There is an example task config in the resources directory.
You would run the sid migration by starting server like this:
<regular jar invocation start> -p task -c <path-to-task-config>