Please make sure these boxes are checked before submitting your PR - thank you!

• [x] Pull request is based against develop branch
• [x] README.md reflects changes (if applicable)
• [x] New files contain a license header

Issue

This PR fixes issue #15 .

Proposed changes

Due to the fact that configuration path can have more than 3 parts (separated by /), in the abstract writer we get the first 2 parts normally and use the rest as the third part. E.g:

Suppose we have this configuration in database:

system/full_page_cache/varnish/access_list => localhost
system/full_page_cache/varnish/backend_host => localhost
system/full_page_cache/varnish/backend_port => 8080

Before the PR, this is the exported yaml configuration

system:
  full_page_cache:
    varnish:
      default:
        - '8080'

After PR

system:
  full_page_cache:
    varnish/access_list:
      default:
        - localhost
    varnish/backend_host:
      default:
        - localhost
    varnish/backend_port:
      default:
        - '8080'

There's no change to the reader though as the configuration is parsed correctly either way

Has there been any thought or desire to include the ability to import secret config (api user/password, merchant ids, etc) via environment variables? I might pick this up unless there has already been some work done somewhere else, or opinions on how to handle this differently.

Please make sure that you provide as much information as possible. If you have an example files, which reflect the issue, please make sure to attach them to the issue - thank you!

General

• Module version: 3.10.0
• Magento version: 2.4.5-p1
• PHP version: 8.1.11

Issue description

In ErrorHandler.php line 62:

  Deprecated Functionality: preg_replace_callback(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /var/www/html/ve
  ndor/semaio/magento2-configimportexport/Model/Resolver/EnvironmentVariableResolver.php on line 31

Steps to reproduce

1. run config import with a value (that was exported before) like:

tax/defaults/postcode:
  default:
    0:

Please make sure that you provide as much information as possible. If you have an example files, which reflect the issue, please make sure to attach them to the issue - thank you!

General

• Module version: 3.x
• Magento version: 2.4.4
• PHP version: 8.1.5

Issue description

Any plans to update this module for magento 2.4.4 and php 8.1.x?

General

• Module version: 3.3.0
• Magento version: 2.4.1
• PHP version: 7.4

Issue description

I created a new Magento 2.4.1 project and installed the semaio/magento2-configimportexport package afterward as described in the README file. When invoking bin/magento the commands exposed by the module are not listed and I cannot invoke them.

I could track things down to this: Currently, the module is registering the commands with type Magento\Framework\Console\CommandList. When changing the type to Magento\Framework\Console\CommandListInterface the commands appear when invoking bin/magento .

This is also mentioned in the README file of the Console package: https://github.com/magento/magento2/blob/2.4-develop/lib/internal/Magento/Framework/Console/README.md

Happy to provide a PR if changing the type makes sense for you.

Issue

Currently single quotes in config values are escaped using backslashes (i.e., 'testing \' 123'), but this is not valid YAML and causes Symfony to throw an exception when the values are imported back into the database.

Proposed changes

Correctly quote single quotes with a repeated single quote (i.e., 'testing '' 123').

General

• Module version: 2.0.0
• Magento version: EE 2.1.5
• PHP version: 7.0.15

Issue description

Magneto use a config with path crontab/default/jobs/magento_scheduled_import_export_log_clean/schedule/cron_expr to store the cron schedule of import/export log cleaning schedule options (See \Magento\ScheduledImportExport\Model\System\Config\Backend\Logclean\Cron::CRON_STRING_PATH). This is exported as crontab/default/jobs. Once the exported file is imported, it will basically discard all crontab configuration (defined in crontab.xml of modules) and result in error when attempt to run cron.

Steps to reproduce

1. In Magento backend, Go to Store > Configuration > Advanced > System
2. Click save
3. Export config
4. Import exported files
5. Try to run cron (bin/magento cron:run)
6. See error invalid argument supplied to foreach

Please make sure these boxes are checked before submitting your PR - thank you!

• [x] Pull request is based against develop branch - no, there is no develop branch
• [x] README.md reflects changes (if applicable)
• [x] New files contain a license header

Issue

This PR fixes issue #20.

Proposed changes

I took the existing PR #21 and processed @ktomk his suggestions, and added a description to the docs.

The YAML parser actually returns mixed results but previous non-array cases could not be handled.

Additionally if a file is being skipped more information is provided.

Please make sure these boxes are checked before submitting your PR - thank you!

• [ ] Pull request is based against develop branch
• [ ] README.md reflects changes (if applicable)
• [ ] New files contain a license header

Issue

This PR fixes issue #54.

Proposed changes

...

With Symfony Yaml >= 3.0 the option to pass a filename was removed. The commit 6c959b8c56a9e027e2f3727cc9719681e1fe2f8e introduces the compatibilty with >=3.0.

To support 2.0 and 3.0 of Symfony Yaml we need get the file contents in the YamlReader.

Also see: Yaml.php @ v2.8 https://github.com/symfony/yaml/blob/2.8/Yaml.php#L58 Yaml.php @ v3.3 https://github.com/symfony/yaml/blob/3.3/Yaml.php#L52

The file_get_contents is no longer there.

Please make sure these boxes are checked before submitting your PR - thank you!

• [ ] Pull request is based against develop branch
• [ ] README.md reflects changes (if applicable)
• [ ] New files contain a license header

Issue

This PR fixes issue # .

Proposed changes

...

• [X] Pull request is based against main branch
• [X] README.md reflects changes (if applicable)
• [X] New files contain a license header

Issue

This PR fixes issue #60.

Proposed changes

Based on the response from @therouv this PR implements a new --filepath option for the export command.

I believe these changes offer greater flexibility while also improving the default behaviour:

• --filepath Path into which the export should be written. Defaults to var/semaio/config_export/Ymd_His/.
• --filename Filename into which the export should be written. Defaults to config.

First of all, thanks for this module; Zookal/HarrisStreet-ImpEx was one of my favourite and most-used M1 magerun tools so it is great to see it recreated and re-imagined for M2.

One thing I wonder is whether we can have greater control of the export directory using the --filename parameter. Currently it will always export to var/Ymd_His followed by either config or the value of the --filename parameter and then optionally the namespace.

This isn't very flexible. For example, for my workflow I like to keep a copy of the dumped export in git, but currently it always dumps to a new directory because we can't remove the Ymd_His part of the export path so this then requires a manual step to copy or move everything into a consistent directory.

Also, a lesser issue than the timestamping is that I might not want the data in var at all but possibly somewhere else. Setting --filename on HarrisStreet-ImpEx provided complete run-time override of the full output directory path.

I appreciate that emulating the HarrisStreet-ImpEx behaviour and allowing to completely override the path using --filename would be a breaking change for existing workflows so this may not be a popular idea.

However, a simple solution to the timestamping with no breaking changes would be to add a --timestamp (-t) parameter which defaults to true and if set to false will remove the timestamp portion of the export path. For me personally this would be a huge improvement in usability and come with no cost that I can see.

What do you think? I could do a PR for the latter if it would be useful?