Properies

  • It is strongly recommended that, by default, the value for custom-configuration-dir is <magento-install-directory>/app/etc/configuration

  • As soon as a default configuration is copied, changed, extended, or modified and stored under the path specified in custom-configuration-dir, only this configuration takes effect and always overwrites the original configuration

  • The configuration handling is mainly based on the PHP framework Symfony, and therefore unexpected effects maid occur in different configuration constellations

    • Consequently, it is always recommended to test modified configurations concerning unwanted side effects

The configuration file is divided into the following described standard configuration sections and can include the following properties:

Following examples are based on a configuration during initial installation

additional-vendor-dirs

Property
Property Name Default Description

additional-vendor-dirs

[]

With additional-vendor-dirs additional vendor directories can be specified.

When installing with the PHAR version of Pacemaker Community Edition, it is required to use the additional-vendor-dirs directive.
Example 1
In a existing configuration file
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  "system-name": "12345-mbp",
  ...,
  "additional-vendor-dirs" : [
    {
      "vendor-dir": "vendor",
      "relative": true,
      "libraries": [
        "techdivision/import-adapter-custom"
      ]
    }
  ]...,
}
Example 2
As a custom override configuration file
{
  "additional-vendor-dirs" : [
    {
      "vendor-dir": "vendor",
      "relative": true,
      "libraries": [
        "techdivision/import-adapter-custom"
      ]
    }
  ]
}

archive-dir

Property
Property Name Default Description

archive-dir

</path/to/my/archive/dir>
The option --archive-dir can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  "system-name": "12345-mbp",
  ...,
  "archive-dir" : "<archive/dir/path>",
  ...,
}
CLI
import:execute --archive-dir="<OptionValue>"

aliases

Overriding classes can be dangerous and should only be done when you aware of what you’re doing
Property
Property Name Default Description

aliases

[]

Aliases can be used to override classes with custom functionality, e.g. provided by a project-specific library.

As example, if a custom adapter for caching is used, the default class behind the Symfony DI configuration of the cache.adapter can be replaced by the customer DI identifier import_parallel.cache.adapter.redis in a snippet, e.g. <custom-installation-dir>/aliases.json.
Example
<custom-installation-dir>/aliases.json
{
  "aliases": [
    {
      "id": "cache.adapter",
      "target": "import_parallel.cache.adapter.redis"
    }
  ]
}

archive-artefacts

Property
Property Name Default Description

archive-artefacts

true
The option --archive-artefacts can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  "operation-name": "add-update",
  "debug-mode": false,
  ...
  "archive-artefacts": true, (1)
  ...
}
1 The archive-artefacts option can be set as true|false value
CLI
import:execute --archive-artefacts="<OptionValue>"

configuration

Property
Property Name Default Description

configuration

</path/to/my/configuration/file>
The option --configuration can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.1",
  "operation-name" : "replace",
  ...
  "configuration" : "app/etc/configuration/",
  ...
}
CLI
import:clear:pid-file --configuration="<OptionValue>"

custom-configuration-dir

Property
Property Name Default Description

custom-configuration-dir

<app/etc/custom-configuration/dir/>
The option --custom-configuration-dir can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.1",
  "operation-name" : "replace",
  ...
  "custom-configuration-dir" : "<app/etc/custom-configuration-dir/>",
  ...
}
CLI
import:execute --custom-configuration-dir="<OptionValue>"

cache-enabled

Property
Property Name Default Description

cache-enabled

false
The option --cache-enabled can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  "system-name": "12345-mbp",
  "image-types": [],
  "single-transaction": false,
  ...,
  "cache-enabled": false,
  ...,
  "aliases": [],
}
CLI
import:execute --cache-enabled="<OptionValue>"

clear-artefacts

Property
Property Name Default Description

clear-artefacts

true
The option --clear-artefacts can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  "operation-name": "add-update",
  "debug-mode": false,
  ...
  "clear-artefacts": true, (1)
  ...
}
1 The clear-artefacts option can be set as true|false value
CLI
import:execute --clear-artefacts="<OptionValue>"

databases

Property
Property Name Default Description

databases

[]

  • value is generated automatically

A user-defined database connection can be specified; the databases property of the type array contains the selected database access data.

Depending on the command-line option --use-db-id and the specified value, the database with the given ID will be used.

  • If the command-line options are not specified, the one with the flag "default": true will be used.

  • If not found, the first configured database will get used.

  • If a value for the command-line option --db-pdo-dsn has been specified, the --use-db-id option will get ignored, and the given DSN value will be used for database connection instead.

  • In addition, the credentials, by using the --db-username and --db-password options, also need to be specified.

The database configuration gets used if there is a need to access a separate database, e.g., for testing purposes or when running Pacemaker Community Edition standalone.

The default for Magento is the Magento own database configuration from the env.php file.
Example
{
  "databases": [
    {
      "id": "local",
      "default": false, (1)
      "pdo-dsn": "mysql:host=127.0.0.1;dbname=appserver_magento2_ee212",
      "username": "your-username",
      "password": "your-password"
    },
    {
      "id": "remote",
      "default": true, (2)
      "pdo-dsn": "mysql:host=127.0.0.130;dbname=appserver_magento2_ee212",
      "username": "your-username",
      "password": "your-password"
    }
  ]
}
1 If no command-line options are found, the first configured database will get used
2 If the command-line options are not specified, the one with the flag "default": true will be used

db-password

Property
Property Name Default Description

db-password
The option --db-password can get used with the following CLI commands:
CLI
import:execute --db-password="<OptionValue>"

dest

Property
Property Name Default Description

dest
The option --dest can get used with the following CLI commands:
Example
CLI
import:create:configuration-file --dest="<OptionValue>"

db-pdo-dsn

Property
Property Name Default Description

db-pdo-dsn
The option --db-pdo-dsn can get used with the following CLI commands:
CLI
import:execute --db-pdo-dsn="<OptionValue>"

db-table-prefix

Property
Property Name Default Description

db-table-prefix
The option --db-table-prefix can get used with the following CLI commands:
CLI
import:execute --db-table-prefix="<OptionValue>"

db-username

Property
Property Name Default Description

db-username
The option --db-username can get used with the following CLI commands:
CLI
import:execute --db-username="<OptionValue>"

default-values

Property
Property Name Default Description

default-values

{…​}

See a more detailed description to default-values
Example
{
  "default-values": {
    "catalog_product": {(1)
      "my-column": "my-column-value",(2)
    }
  }
}
1 Entity Type code section, Available Entity Type Code
2 For each user-defined field, a key-value pair can get specified

debug-mode

Property
Property Name Default Description

debug-mode

false
The option --debug-mode can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  "operation-name": "add-update",
  "archive-artefacts": false,
  ...
  "debug-mode": false,
  ...
}
CLI
import:execute --debug-mode="<OptionValue>"

empty-attribute-value-constant

Property
Property Name Default Description

empty-attribute-value-constant
The option --empty-attribute-value-constant can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  ...
  "empty-attribute-value-constant": "__CUSTOM_CONSTANT__EMPTY__VALUE__",
  ...
}
CLI
import:execute --empty-attribute-value-constant="<OptionValue>"

entity-type-code

Property
Property Default Description

entity-type-code

none

Pacemaker support Magento Eav Entity Types

All listed Entity Types below are available with Pacemaker.

Pacemaker entity types:

  • customer

  • customer_address

  • catalog_category

  • catalog_product

  • eav_attribute

  • eav_attribute_set

  • catalog_product_inventory_msi

  • catalog_product_tier_price

  • catalog_product_url

  • debug

  • company_entity (professional version)

  • catalog_product_custom_option (professional version)

  • catalog_product_fpt (professional version)

  • sales_gift_card (professional version)

Be sure to specify the correct category configuration file with the option --configuration=<path/to/your-category-configuration>.json; alternatively you can pass the path to the default category configuration.
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  "operation-name": "add-update",
  "archive-artefacts": false,
  "debug-mode": false,
  ...
  "entity-type-code": "catalog_product",
  ...
}
CLI
import:create:ok-file --entity-type-code="<OptionValue>"

extension-libraries

Property
Property Name Default Description

extension-libraries

[]

For more complex projects, additional libraries may get needed.

Pacemaker Community Edition Console Tool uses Symfony DI container. Therefore, it is necessary to register other libraries by adding them to the configuration file.
Example 1
Default after inital installation
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  ...,
  "extension-libraries": [],
  ...,
}
Example 2
Add a additional extension library using a custom configuration file (app/etc/configuration/extension-libraries.json)
{
  "extension-libraries" : [
    "techdivision/import-product-magic360"
  ]
}

header-mappings

Property
Property Name Default Description

header-mappings

[…​]
Example 1
Default header-mappings setting in configurations.json
{
  "header-mappings": {
    "catalog_product": {
      "my_sku_column": "sku",
      "my_qty_column": "qty",
      ...,
    }
  }
}
  ...
}

image-types

Property
Property Name Default Description

image-types

[]

image-types allow us to set different Magento image types for the import as available table columns.

By default, all Magento standard image types get specified in Pacemaker Community Edition, and under specification or as default [] is set and all provided types are supported.

  • Magento standard image types

    • base_image

    • small_image

    • thumbnail_image

    • additional_images

Once one or more types get listed in the given array, Pacemaker Community Edition assumes that only the listed image types need to get imported.
Example 1
Default
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  "system-name": "12345-mbp",
  ...,
  "image-types": [],
  ...,
}
Example 2
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  "system-name": "12345-mbp",
  ...,
  "image-types": [
    "base_image",
    "small_image",
    "thumbnail_image",
    "additional_images"
  ],
  ...,
}

installation-dir

Property
Property Default Description

installation-dir

</path/to/my/project/root>
The option --installation-dir can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.1",
  "operation-name" : "replace",
  "table-prefix": "test_",
  ...
  "installation-dir" : "/Volumes/workspace/www/myproject",
  ...
}
CLI
Example
import:execute --installation-dir="<OptionValue>"

listeners

Property
Property Name Default Description

listeners

[]

By default, Pacemaker Community Edition comes with several listeners registered

  • See example
Example
{
  "listeners": [
    {
      "app.set.up": [
        "import.listener.render.ansi.art", (1)
        "import.listener.render.operation.info",
        "import.listener.render.mysql.info",
        "import.listener.render.debug.info",
        "import.listener.initialize.registry"
      ],
      "app.process.transaction.success": [ (2)
        "import.listener.finalize.registry",
        "import.listener.archive",
        "import.listener.clear.artefacts",
        "import.listener.clear.directories",
        "import.listener.operation.report"
      ],
      "app.process.transaction.failure": [ (3)
        "import.listener.finalize.registry",
        "import.listener.render.validations"
      ],
      "app.tear.down": [
        "import.listener.import.history",
        "import.listener.clear.registry"
      ]
    }
  ]
}
1 The first listener named import.listener.render.ansi.art renders the ASCII graphic image when the CLI gets called
2 The second part is mandatory as it is responsible for initializing the registry of the actual import
3 The third part is mandatory as it is responsible for initializing the registry of the actual import

As a solution partner, feel free to replace the ASCII art renderer with one of your choices, e.g., rendering your company logo

loggers

Pacemaker Import Community uses Monolog to provide the basic logging functionality.

Property
Property Name Default Description

loggers

{…}

  • One logger instance is necessary

    • As a minimum requirement, at least one logger instance gets needed

    • By default, if no logger is configured, a system logger is installed that writes log messages to the error log set in the php.ini file of the PHP installation used

Additional loggers

E.g., to send emails when an exception gets thrown, the configuration can be extended as follows, with a custom <custom-configuration-dir>/loggers.json snippet.
Example 1
{
  "loggers": {
    "system": {
      "channel-name": "logger/system",
      "id": "import.logger.factory.monolog",
      "processors": [
        {
          "id": "import.logger.processor.serial",
          "params": [],
          "param-delimiter": ","
        },
        {
          "id": "import.logger.processor.memory.peak.usage",
          "params": [],
          "param-delimiter": ","
        }
      ],
      "handlers": [
        {
          "id": "import.logger.factory.handler.stream.wrapper",
          "formatter": {
            "id": "import.logger.factory.formatter.line",
            "params": {
              "format": "[%datetime%] %channel%.%level_name%: %message% %context% %extra%
              ",
              "date-format": "Y-m-d H:i:s",
              "allow-inline-line-breaks": true,
              "ignore-empty-context-and-extra": true
            },
            "param-delimiter": ","
          },
          "params": {
            "stream": "system.log",
            "level": "info"
          },
          "param-delimiter": ","
        },
        {
          "id": "import.logger.factory.handler.stream.wrapper",
          "formatter": {
            "id": "import.logger.factory.formatter.line",
            "params": {
              "format": "[%datetime%] %channel%.%level_name%: %message% %context% %extra%
              ",
              "date-format": "Y-m-d H:i:s",
              "allow-inline-line-breaks": true,
              "ignore-empty-context-and-extra": true
            },
            "param-delimiter": ","
          },
          "params": {
            "relative": false,
            "stream": "php://stdout",
            "level": "notice"
          },
          "param-delimiter": ","
        }
      ],
      "params": [],
      "param-delimiter": ","
    }
  }
}
Example 2
There is also a possibility to use Handler for Native Mail Sender, which takes over PHP configuration settings.
{
  "loggers": {
    "mail": {
      "id": "import.logger.factory.monolog",
      "channel-name": "logger/mail",
      "handlers": [
        {
          "id": "import.logger.factory.handler.swift",
          "formatter": {
            "id": "import.logger.factory.formatter.line",
            "params": {
              "format": "[%datetime%] %channel%.%level_name%: %message% %context% %extra%",
              "date-format": "Y-m-d H:i:s",
              "allow-inline-line-breaks": true,
              "ignore-empty-context-and-extra": true
            }
          },
          "params": {
            "log-level": "error", (1)
            "bubble": false
          },
          "swift-mailer" : {
            "id" : "import.logger.factory.transport.swift.smtp",
            "params" : {
              "to" : "<to-email-address.com>",
              "from" : "<from-email-address.com>",
              "subject": "<subject-text>",
              "content-type" : "text/plain"
            },
            "transport" : {
              "params" : {
                "smtp-host" : "<smtp-host>",
                "smtp-port" : 25
              }
            }
          }
        }
      ]
    }
  }
}
1 We add a mail logger, and the default log level gets set to error

loggers.mail.handlers

To add additional loggers, e.g. in case you want to send mails if an exception has been thrown, the configuration can get extended, e.g. with a snippet <custom-configuration-dir>/loggers.json.

Property
Property Name Default Description

handlers

  • Handler for Native Mail Sender

    • You can also use a handler for Native Mail Sender, which takes the settings of the PHP configuration

    • The example handler will add a mail logger and set the default log level to error
Example 1
{
  ...,
  "handlers": [
    {
      "id": "import.logger.factory.handler.native.mail.log",
      "formatter": {
        "id": "import.logger.factory.formatter.line",
        "params": {
          "format": "[%datetime%] %channel%.%level_name%: %message% %context% %extra%",
          "date-format": "Y-m-d H:i:s",
          "allow-inline-line-breaks": true,
          "ignore-empty-context-and-extra": true
        }
      },
      "params": {
        "to": [
          "<to-email-address.com>"
        ],
        "subject": "<subject-text>",
        "from": "<from-email-address.com>",
        "level": "error", (1)
        "bubble": true,
        "maxColumnWidth": 500
      }
    }
  ],
  ...
}
1 The mail logger sets the default log level to error
Example 2
{
  "loggers": {
    "mail": {
      "id": "import.logger.factory.monolog",
      "channel-name": "logger/mail",
      "handlers": [
        {
          "id": "import.logger.factory.handler.native.mail.log",
          "formatter": {
            "id": "import.logger.factory.formatter.line",
            "params": {
              "format": "[%datetime%] %channel%.%level_name%: %message% %context% %extra%",
              "date-format": "Y-m-d H:i:s",
              "allow-inline-line-breaks": true,
              "ignore-empty-context-and-extra": true
            }
          },
          "params": {
            "to": [
              "<to-email-address.com>"
            ],
            "subject": "<subject-text>",
            "from": "<from-email-address.com>",
            "level": "error",
            "bubble": true,
            "maxColumnWidth": 500
          }
        }
      ]
    }
  }
}

log-level

Property
Property Name Default Description

log-level

info
The option --log-level can get used with the following CLI commands:
Example
{
  "loggers": {
    "mail": {
      "id": "import.logger.factory.monolog",
      ...,
      "handlers": [
        {
          "id": "import.logger.factory.handler.swift",
          ...,
          "params": {
            "log-level": "error",
            ...
          },
          ...
        }
      ]
    }
  }
}
CLI
import:execute --log-level="<OptionValue>"

magento-edition

Property
Property Default Description

magento-edition

CE|PE|EE
The option --magento-edition can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  "system-name": "12345-mbp",
  ...,
}
CLI
Example
import:execute --magento-edition="<OptionValue>"

magento-version

Property
Property Name Default Description

magento-version

x.x.x
The option --magento-version can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  "system-name": "12345-mbp",
  ...,
}
CLI
Example
import:execute --magento-version="<OptionValue>"

move-files-prefix

Property
Property Name Default Description

move-files-prefix

<Defaults to the prefix of the first plugin subject>
The option --move-files-prefix can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  ...
  "move-files-prefix": "admin",
  ...
}
CLI
import:execute --move-files-prefix="<OptionValue>"

multiple-field-delimiter

Property
Property Name Default Description

multiple-field-delimiter
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.2",
  "operation-name" : "add-update",
  "installation-dir" : "/var/www/magento",
  "multiple-field-delimiter" : ",",
  "multiple-value-delimiter" : "|",
  "databases" : [ ... ],
  "loggers" : [ ... ],
  "operations" : { ... }
}

multiple-value-delimiter

Property
Property Name Default Description

multiple-value-delimiter
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.2",
  "operation-name" : "add-update",
  "installation-dir" : "/var/www/magento",
  "multiple-field-delimiter" : ",",
  "multiple-value-delimiter" : "|",
  "databases" : [ ... ],
  "loggers" : [ ... ],
  "operations" : { ... }
}

operations

Property
Property Name Default Description

operations

[]

  • An operation represents a single step of an import command, such as add-update, and combines the required functions as a container

  • An operation allows to add a user-defined configuration (e.g., app/etc/configuration/operations.json) for an existing operation or to create a new operation
Example 1
operation section as a custom operations.json file
{
  "operations": {
    "general": {
      "catalog_product_tier_price": {
        "add-update": {
          "plugins": {
            "subject": {
              "id": "import.plugin.subject",
              "listeners": [
                {
                  "plugin.process.success": [
                    "import_product_tier_price.listener.delete.obsolete.tier_prices"
                  ]
                }
              ],
              "subjects": [ ... ]
            }
          }
        }
      }
    }
  }
}
Example 2
operation section in a configuration.json file
{
  "system-name": "00752-mbp",
  "entity-type-code": "none",
  "installation-dir": "<magento-install-dir>",
  "magento-edition": "CE",
  "magento-version": "2.2.0",
  "databases": [],
  ...,
  "operations": {
    "general": {
      "general": {
        "create-ok-files": {
          "plugins": [
            {...}
        },
        ...
      },
      ...
    },
    "ce": {...},
    "ee": {...}
  },
  "extension-libraries": [],
  ...
}

params

Property
Property Name Default Description

params

{…​}
The option --params can get used with the following CLI commands:
Example
{
  "params": {
    "my-website-country-mapping": {
      "DE": [ "de_DE", "de_AT", "de_CH" ],
      "EN": [ "en_US", "en_UK" ]
    }
  }
}
CLI
import:products --params="<OptionValue>"
Example how to pass parameter
import:products --params='{ "params": { "my-website-country-mapping": { "DE": [ "de_LI" ] } } }'

param-delimiter

Property
Property Name Default Description

param-delimiter

,

A separator specifies how listed parameter values get separated within an array.
Example
{
  "params": {
    "my-website-country-mapping": {
      "DE": [ "de_DE", "de_AT", "de_CH" ],
      "EN": [ "en_US", "en_UK" ]
    }
  },
  "param-delimiter": ","
}

params-file

Property
Property Name Default Description

params-file
The option --params-file can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.2",
  "operation-name" : "add-update",
  "installation-dir" : "/var/www/magento",
  ...,
  "params-file": "<system-temp-dir>/<custom-configuration-file.json>",
  ...,
}
CLI
import:execute --params-file="<OptionValue>"

pid-filename

Property
Property Name Default Description

pid-filename

  • See a more detailed description to --pid-filename

  • pid-filename is the exact PID file name to be applied for a import process

  • pid-filename is generated when an import gets started

  • pid-filename must only get specified if the import PID is stored at a different location

  • The file pid-filename contains only the import PID, represented as a number

  • pid-filename ensures that only one import process can run

  • The pid-filename file gets removed after each finished import

The option --pid-filename can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.2",
  "operation-name" : "add-update",
  "installation-dir" : "/var/www/magento",
  "multiple-field-delimiter" : ",",
  "multiple-value-delimiter" : "|",
  ...,
  "pid-filename": "<system-temp-dir>/importer.pid",
  ...,
  "databases" : [ ... ],
  "loggers" : [ ... ],
  "operations" : { ... }
}
CLI
import:execute --pid-filename="<OptionValue>"

render-validation-issues

Property
Property Name Default Description

render-validation-issues

100
The option --render-validation-issues can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.2",
  "operation-name" : "add-update",
  "installation-dir" : "/var/www/magento",
  ...,
  "render-validation-issues": "100",
  ...,
}
CLI
import:execute --render-validation-issues="<OptionValue>"

serial

Property
Property Name Default Description

serial
The option --serial can get used with the following CLI commands:
CLI
import:execute --serial="<OptionValue>"

shortcuts

Property
Property Name Default Description

shortcuts

{…​}
The option --shortcuts can get used with the following CLI commands:
Example
{
  "shortcuts": {
    "ce": {
      "catalog_product": {
        "add-update": [
          "general/general/global-data",
          "general/general/move-files",
          "general/catalog_product/collect-data",
          "general/catalog_category/convert",
          "ce/catalog_category/sort",
          "ce/catalog_category/add-update",
          "ce/catalog_category/add-update.path",
          "ce/catalog_category/add-update.url-rewrite",
          "general/catalog_category/children-count",
          "general/catalog_product/validate",
          "ce/catalog_product/add-update",
          "ce/catalog_product/add-update.variants",
          "ce/catalog_product/add-update.bundles",
          "ce/catalog_product/add-update.links",
          "ce/catalog_product/add-update.grouped",
          "ce/catalog_product/add-update.media",
          "general/catalog_product/add-update.msi",
          "general/catalog_product/add-update.url-rewrites"
        ]
      }
    }
  }
}

single-transaction

Property
Property Name Default Description

single-transaction

false
The option --single-transaction can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  "operation-name": "add-update",
  "archive-artefacts": false,
  "debug-mode": false,
  ...
  "cache-enabled": false,
  ...
}
CLI
import:create:ok-file --single-transaction="<OptionValue>"

source-dir

Property
Property Name Default Description

source-dir
The option --source-dir can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  ...,
  "source-dir": "<system-temp-dir>/<directory-name-to-be-monitored>",
  ...,
}
CLI
import:execute --source-dir="<OptionValue>"

strict-mode

Property
Property Name Default Description

strict-mode

true
The option --strict-mode can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  ...,
  "strict-mode": "true",
  ...,
}
CLI
import:execute --strict-mode="<OptionValue>"

system-name

Property
Property Default Description

system-name

<OptionValue e.g. 00752-mbp>
The option --system-name can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  ...,
  "system-name": "12345-mbp",
  ...,
}
CLI
Example
import:execute --system-name="<OptionValue>"

target-dir

Property
Property Name Default Description

target-dir
The option --target-dir can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  ...,
  "target-dir": "<system-temp-dir>/<directory-of-import-files>",
  ...,
}
CLI
import:execute --target-dir="<OptionValue>"

username

Property
Property Name Default Description

username

<username>

The username represents the given username after the Pacemaker Community Edition installation
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  ...
  "username": "admin",
  ...
}

use-db-id

Property
Property Name Default Description

use-db-id
The option --use-db-id can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  ...,
  "use-db-id": "<my-db-id>",
  ...,
}
CLI
import:execute --use-db-id="<OptionValue>"

config-output

Property
Property Name Default Description

config-output
The option --config-output can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  ...,
  "config-output": true,
  ...,
}
CLI
import:debug --config-output="<OptionValue>"

config-dir

Property
Property Name Default Description

config-dir
The option --config-dir can get used with the following CLI commands:
Example
{
  "magento-edition": "CE",
  "magento-version": "2.3.4",
  ...,
  "config-dir": "<directory-path-of-config-dir>",
  ...,
}
CLI
import:execute --config-dir="<OptionValue>"

WIR HÄTTEN IHNEN DIESE MELDUNG AUCH GERNE ERSPART ...

... aber wir müssen Sie informieren, dass wir auf unserer Website Cookies verwenden:
  1. Diese Website verwendet keine technisch notwendigen Cookies.
  2. "Böse" Tracking-Cookies von Google Analytics (natürlich mit IP-Anonymisierung) und Leadfeeder, damit wir unsere Inhalte besser auf Ihre Bedürfnisse anpassen können.
Solange Sie nicht explizit akzeptieren, tracken wir Sie auch nicht.
Versprochen!

Detaillierte Infos in unserer Datenschutzerklärung

P.S.: Während der Entwicklung dieser Website wurden intensiv Chocolate Cookies eingesetzt.
Die sind aber alle schon weg - wir bräuchten bitte neue.
Akzeptieren Verweigern