The configimport subcommand imports configuration objects from the specified directory, enabling you to reuse a system configuration from another environment. For example, you can test a configuration in a development environment, then export it and import it into a production environment.
The command updates the existing configuration from the
import-location over the OpenIDM REST interface.
By default, if configuration objects are present in the
import-location and not in the existing
configuration, these objects are added. If configuration objects are present
in the existing location but not in the
import-location, these objects are left untouched
in the existing configuration.
If you include the --replaceAll parameter, the
command wipes out the existing configuration and replaces it with the
configuration in the import-location. Objects in
the existing configuration that are not present in the
import-location are deleted.
Usage is as follows:
$ ./cli.sh configimport [--replaceAll] /import-location
For example:
$ ./cli.sh configimport --replaceAll /tmp/conf
Configuration objects are imported, as .json files,
from the specified directory to the conf directory. The
configuration objects that are imported are outlined in the corresponding
export command, described in the previous section.
