Magento 2 Configurator

CTI Digital

Last update: Sep 20, 2022

Related tags

Miscellaneous config php configuration magento magento2 magento2-extension magento2-module

Overview

Magento 2 Configurator

A Magento module initially created by CTI Digital to create and maintain database variables using files. This module aims to bring the following benefits to a Magento developer's work flow:

Install Magento from scratch with important database based configuration ready.
Share and collaborate configuration with other colleagues using your own versioning system.
Keep versions of your configurations using your own versioning system.
Split your configuration based on the environment you're developing on.

If you're interested to find out more about the background of the configurator, watch this lightning talk by Raj Chevli at Mage Titans in Manchester on YouTube.

This is a work in progress and by no means for use with production environments (and probably not even development environments either just yet).

Testing Locally For Development

If you are contributing the module, please run the following commands to stand the best chance with Travis CI liking your code. These test include PHP Code Sniffer, PHP Mess Detector, PHP Copy and Paste Detector, PHP Unit

php vendor/bin/phpcs --standard=vendor/magento/magento-coding-standard/Magento2/ruleset.xml vendor/ctidigital/magento2-configurator/Model/ vendor/ctidigital/magento2-configurator/Console/ vendor/ctidigital/magento2-configurator/Test/ vendor/ctidigital/magento2-configurator/Api/ vendor/ctidigital/magento2-configurator/Component/ vendor/ctidigital/magento2-configurator/Exception/
php vendor/bin/phpmd vendor/ctidigital/magento2-configurator/Model/,vendor/ctidigital/magento2-configurator/Console/,vendor/ctidigital/magento2-configurator/Test/,vendor/ctidigital/magento2-configurator/Api/,vendor/ctidigital/magento2-configurator/Component/,vendor/ctidigital/magento2-configurator/Exception/ text cleancode,codesize,controversial,design,naming,unusedcode
php vendor/bin/phpcpd vendor/ctidigital/magento2-configurator/Model/ vendor/ctidigital/magento2-configurator/Console vendor/ctidigital/magento2-configurator/Test/ vendor/ctidigital/magento2-configurator/Api/ vendor/ctidigital/magento2-configurator/Component/ vendor/ctidigital/magento2-configurator/Exception/
php vendor/bin/phpunit vendor/ctidigital/magento2-configurator/Test/Unit/

Integration tests

Configure your Magento integration test environment.
Add the XML below to dev/tests/integration/phpunit.xml.dist

<testsuite name="magento2-configurator">
    <directory>../../../vendor/ctidigital/magento2-configurator/Test/Integration</directory>
</testsuite>

You can run the tests from the correct place on the command line

/dev/tests/integration$ ../../../vendor/bin/phpunit --testsuite "magento2-configurator"

You can also add the magento PHP developer tools to your path, so that you do not have to specify location of phpunit

export PATH=$PATH:/var/www/magento2/vendor/bin

Unit tests

If you're developing a new component, please ensure you have your corresponding unit test which extends ComponentAbstractTestCase as that will test that your component has the required functions. Do also include sample files with your component that works

Travis

We also use Travis CI to automate part of the testing process (we are still looking to add more to this!). It tests the following:

CodeSniffer
MessDetector
Copy & Paste Detection
Unit Tests
Run Configurator (we aim to run it on these versions)
1. Latest 3 minor versions
2. Latest release candidate (allowed to fail)

Getting Started

Create a master.yaml file in <mage_root>/app/etc/. (see Samples/master.yaml)
Enable Modules CtiDigital_Configurator,FireGento_FastSimpleImport.
Run bin/magento configurator:run --env="<environment>"

Usage

Listing available components bin/magento configurator:list
Running individual components bin/magento configurator:run --env="<environment>" --component="config"
Extra logs bin/magento configurator:run --env="<environment>" -v

Roadmap for components to do

Component	Code Written	Tests Written	Sample Files
Websites	✅	❕	✅
System Configuration	✅	❕	✅
Categories	✅	❕	✅
Products	✅	❕	✅
Attributes	✅	❕	✅
Attribute Sets	✅	❕	✅
Blocks	✅	❕	✅
Admin Roles	✅	❕	✅
Admin Users	✅	❕	✅
Pages	✅	❕	✅
Widgets	✅	❕	✅
Customer Groups	✅	❕	✅
Media	✅	❕	✅
Tax Rules	✅	❕	✅
API Integrations	✅	❕	✅
Tax Rates	✅	❕	✅
Rewrites	✅	✅	✅
Review Ratings	✅	✅	✅
Related Products	✅	❕	✅
Up Sell Products	✅	❕	✅
Cross Sell Products	✅	❕	✅
Customers	✅	✅	✅
SQL	✅	✅	✅
Catalog Price Rules	✅	❌	✅
Shipping Table Rates	✅	✅	✅
Customer Attributes	✅	❌	✅
Shopping Cart Price Rules	❌	❌	❌
Orders	❌	❌	❌
Tiered Prices	❌	❌	❌

License

MIT

Comments

composer error

Problem 1 - firegento/fastsimpleimport 1.1.0 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.1.11) does not satisfy that requirement. - ctidigital/magento2-configurator 1.3.0 requires firegento/fastsimpleimport 1.1.0 -> satisfiable by firegento/fastsimpleimport[1.1.0]. - Installation request for ctidigital/magento2-configurator ^1.3 -> satisfiable by ctidigital/magento2-configurator[1.3.0].

opened by alex-granovskiy 10
Processing environment yaml sources
Issue #35 suggests that you should be able to specify specific source yaml files that only run on certain environments, such as a local.yaml with special configuration for the local environment, like so:

config: enabled: 1 method: code sources: - ../configurator/Configuration/global.yaml env: local: sources: - ../configurator/Configuration/local.yaml

This didn't seem to work, however. I couldn't find any place in the code where the process() method was actually being called on the ['env'][$this->getEnvironment()]['sources'] array.

I added it here, and it appears to work as expected. Feel free to fix or replace this code as you see fit, but this is where the main sources are processed, and the presence of an environment sources array is being validated here, so it made sense to process it here after the validation.

Thank for the great module, it's just what we were looking for to set up environment specific configuration, and default categories!
opened by thaddeusmt 4
Addition of Customer Group Creation functionality

Created sample + Component file for creation. Yaml file is sectioned into Tax Classes for easier reading and less chance of spelling mistakes due to un-needed repetition.

opened by furan917 3
Admin/API Role + User creation functionality added

Added the ability to create new Admin User Roles.

Yaml file takes name of Role and a list of Resource IDs to create role. List of all avaliable ResourceIds added for lookup If user already exists and resources not empty, user resources will be updated.

opened by furan917 3
Add flag to gracefully continue if source .yaml files don't exist

Currently, if a .yaml file defined in master.yaml does not exist, the configurator:run command fails with an error message:

Could not find file in path /path/to/my/file.yaml

Is it possible to add a command line flag (such as '-i', or '--ignore-missing-files') so that configurator:run just outputs a message to say it's skipping the missing file in this scenario, then proceeds with the rest?
Enhancement

opened by rick-cti 2
Remove magento/framework requirement from composer.json

As we have already have "type":"magento2-module" in the composer.json, magento/framework should not be required. https://github.com/ctidigital/magento2-configurator/blob/d0eabed2b0b88f3bf9718a72f997e155bc802c1d/composer.json#L14
Help Wanted

opened by chevli 2
Master YAML does not exist. Please create one in /var/www/html/app/etc/master.yaml in magento 2.1.8
I have copied the master.yml in the sample to my app/etc/master.yml. But when I run this command magento configurator --env=local I got this error :

Master YAML does not exist. Please create one in /var/www/html/app/etc/master.yaml

it is weird error even though the file is exist in app/etc any idea ?
opened by Gujarats 2
Add environment examples to documentation

I heard of this module via the twittersphere and am intrigued. I think it'd be really helpful in getting some of the stores I am working on up and running.

What I am not sure of is how to implement different configuration based on the environment. The example commands show an environment being passed in, but where do I actually specify that configuration. So for example I want to enable debug mode of a module in development and staging, but not in production. Is that possible, and if so how? Or as per the example master.yml file, is the env var specifically only meant for setting the log level and mode?

Keep up the great work!

opened by alanablett 2
composer conflict on magento 2.2.5

I have a fresh install of magento 2.2.5 and i tried to install ctidigital/magento2-configurator

This is my log of the process

composer require ctidigital/magento2-configurator --ignore-platform-reqs Using version ^1.4 for ctidigital/magento2-configurator ./composer.json has been updated Loading composer repositories with package information Updating dependencies (including require-dev) Your requirements could not be resolved to an installable set of packages.

Problem 1 - Conclusion: don't install ctidigital/magento2-configurator 1.4.1 - Conclusion: remove symfony/console v2.8.42 - Conclusion: don't install symfony/console v2.8.42 - symfony/yaml v3.4.0 conflicts with symfony/console[v2.8.42]. - symfony/yaml v3.4.1 conflicts with symfony/console[v2.8.42]. - symfony/yaml v3.4.10 conflicts with symfony/console[v2.8.42]. - symfony/yaml v3.4.11 conflicts with symfony/console[v2.8.42]. - symfony/yaml v3.4.12 conflicts with symfony/console[v2.8.42]. - symfony/yaml v3.4.2 conflicts with symfony/console[v2.8.42]. - symfony/yaml v3.4.3 conflicts with symfony/console[v2.8.42]. - symfony/yaml v3.4.4 conflicts with symfony/console[v2.8.42]. - symfony/yaml v3.4.5 conflicts with symfony/console[v2.8.42]. - symfony/yaml v3.4.6 conflicts with symfony/console[v2.8.42]. - symfony/yaml v3.4.7 conflicts with symfony/console[v2.8.42]. - symfony/yaml v3.4.8 conflicts with symfony/console[v2.8.42]. - symfony/yaml v3.4.9 conflicts with symfony/console[v2.8.42]. - symfony/yaml v4.0.0 conflicts with symfony/console[v2.8.42]. - symfony/yaml v4.0.1 conflicts with symfony/console[v2.8.42]. - symfony/yaml v4.0.10 conflicts with symfony/console[v2.8.42]. - symfony/yaml v4.0.11 conflicts with symfony/console[v2.8.42]. - symfony/yaml v4.0.12 conflicts with symfony/console[v2.8.42]. - symfony/yaml v4.0.2 conflicts with symfony/console[v2.8.42]. - symfony/yaml v4.0.3 conflicts with symfony/console[v2.8.42]. - symfony/yaml v4.0.4 conflicts with symfony/console[v2.8.42]. - symfony/yaml v4.0.5 conflicts with symfony/console[v2.8.42]. - symfony/yaml v4.0.6 conflicts with symfony/console[v2.8.42]. - symfony/yaml v4.0.7 conflicts with symfony/console[v2.8.42]. - symfony/yaml v4.0.8 conflicts with symfony/console[v2.8.42]. - symfony/yaml v4.0.9 conflicts with symfony/console[v2.8.42]. - symfony/yaml v4.1.0 conflicts with symfony/console[v2.8.42]. - symfony/yaml v4.1.1 conflicts with symfony/console[v2.8.42]. - Conclusion: don't install symfony/dependency-injection v4.1.1|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.10|install symfony/yaml v3.4.11|install symfony/yaml v3.4.12|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v3.4.9|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.10|install symfony/yaml v4.0.11|install symfony/yaml v4.0.12|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8|install symfony/yaml v4.0.9|install symfony/yaml v4.1.0|install symfony/yaml v4.1.1 - Conclusion: don't install ctidigital/magento2-configurator 1.4.1|remove symfony/dependency-injection v4.1.1|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.10|install symfony/yaml v3.4.11|install symfony/yaml v3.4.12|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v3.4.9|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.10|install symfony/yaml v4.0.11|install symfony/yaml v4.0.12|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8|install symfony/yaml v4.0.9|install symfony/yaml v4.1.0|install symfony/yaml v4.1.1 - Conclusion: don't install ctidigital/magento2-configurator 1.4.1|don't install symfony/dependency-injection v4.1.1|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.10|install symfony/yaml v3.4.11|install symfony/yaml v3.4.12|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v3.4.9|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.10|install symfony/yaml v4.0.11|install symfony/yaml v4.0.12|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8|install symfony/yaml v4.0.9|install symfony/yaml v4.1.0|install symfony/yaml v4.1.1 - Installation request for symfony/console (locked at v2.8.42) -> satisfiable by symfony/console[v2.8.42]. - Conclusion: don't install ctidigital/magento2-configurator 1.4.1|remove symfony/dependency-injection v4.1.1|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.10|install symfony/yaml v3.4.11|install symfony/yaml v3.4.12|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v3.4.9|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.10|install symfony/yaml v4.0.11|install symfony/yaml v4.0.12|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8|install symfony/yaml v4.0.9|install symfony/yaml v4.1.0|install symfony/yaml v4.1.1 - Conclusion: don't install ctidigital/magento2-configurator 1.4.1|don't install symfony/dependency-injection v4.1.1|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.10|install symfony/yaml v3.4.11|install symfony/yaml v3.4.12|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v3.4.9|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.10|install symfony/yaml v4.0.11|install symfony/yaml v4.0.12|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8|install symfony/yaml v4.0.9|install symfony/yaml v4.1.0|install symfony/yaml v4.1.1 - Installation request for ctidigital/magento2-configurator ^1.4 -> satisfiable by ctidigital/magento2-configurator[1.4.0, 1.4.1]. - Conclusion: remove symfony/dependency-injection v4.1.1|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.10|install symfony/yaml v3.4.11|install symfony/yaml v3.4.12|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v3.4.9|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.10|install symfony/yaml v4.0.11|install symfony/yaml v4.0.12|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8|install symfony/yaml v4.0.9|install symfony/yaml v4.1.0|install symfony/yaml v4.1.1 - ctidigital/magento2-configurator 1.4.0 requires symfony/yaml >2.8.0 -> satisfiable by symfony/yaml[v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.40, v2.8.41, v2.8.42, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.17, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.10, v3.4.11, v3.4.12, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v3.4.9, v4.0.0, v4.0.1, v4.0.10, v4.0.11, v4.0.12, v4.0.2, v4.0.3, v4.0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8, v4.0.9, v4.1.0, v4.1.1]. - symfony/yaml v2.8.1 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.10 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.11 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.12 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.13 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.14 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.15 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.16 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.17 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.18 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.19 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.2 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.20 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.21 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.22 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.23 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.24 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.25 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.26 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.27 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.28 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.29 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.3 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.30 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.31 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.32 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.33 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.34 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.35 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.36 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.37 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.38 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.39 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.4 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.40 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.41 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.42 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.5 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.6 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.7 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.8 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v2.8.9 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.0.0 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.0.1 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.0.2 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.0.3 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.0.4 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.0.5 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.0.6 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.0.7 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.0.8 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.0.9 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.1.0 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.1.1 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.1.10 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.1.2 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.1.3 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.1.4 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.1.5 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.1.6 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.1.7 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.1.8 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.1.9 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.2.0 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.2.1 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.2.10 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.2.11 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.2.12 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.2.13 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.2.14 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.2.2 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.2.3 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.2.4 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.2.5 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.2.6 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.2.7 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.2.8 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.2.9 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.0 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.1 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.10 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.11 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.12 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.13 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.14 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.15 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.16 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.17 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.2 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.3 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.4 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.5 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.6 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.7 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.8 conflicts with symfony/dependency-injection[v4.1.1]. - symfony/yaml v3.3.9 conflicts with symfony/dependency-injection[v4.1.1]. - Installation request for symfony/dependency-injection (locked at v4.1.1) -> satisfiable by symfony/dependency-injection[v4.1.1].

Installation failed, reverting ./composer.json to its original content.

My composer.json file is as follows.

{ "name": "magento/project-community-edition", "description": "eCommerce Platform for Growth (Community Edition)", "type": "project", "version": "2.2.5", "license": [ "OSL-3.0", "AFL-3.0" > ], "require": { "magento/product-community-edition": "2.2.5", "composer/composer": "@alpha" }, "require-dev": { "phpunit/phpunit": "~6.2.0", "squizlabs/php_codesniffer": "3.2.2", "phpmd/phpmd": "@stable", "pdepend/pdepend": "2.5.2", "friendsofphp/php-cs-fixer": "~2.2.1", "lusitanian/oauth": "~0.8.10", "sebastian/phpcpd": "2.0.4" }, "autoload": { "psr-4": { "Magento\Framework\": "lib/internal/Magento/Framework/", "Magento\Setup\": "setup/src/Magento/Setup/", "Magento\": "app/code/Magento/" }, "psr-0": { "": [ "app/code/" > ] }, "files": [ "app/etc/NonComposerComponentRegistration.php" > ], "exclude-from-classmap": [ "/dev/", "/update/", "/Test/" > ] }, "autoload-dev": { "psr-4": { "Magento\Sniffs\": "dev/tests/static/framework/Magento/Sniffs/", "Magento\Tools\": "dev/tools/Magento/Tools/", "Magento\Tools\Sanity\": "dev/build/publication/sanity/Magento/Tools/Sanity/", "Magento\TestFramework\Inspection\": "dev/tests/static/framework/Magento/TestFramework/Inspection/", "Magento\TestFramework\Utility\": "dev/tests/static/framework/Magento/TestFramework/Utility/" } }, "minimum-stability": "stable", "repositories": [ { "type": "composer", "url": "https://repo.magento.com/" } > ], "extra": { "magento-force": "override" } }

opened by rafashkembi 1
Add Catalog Price Rules Component
This PR add catalog price rules component

It contains

Configuration Component implementation

Unit Tests

Integration Tests

master.yaml sample update

catalog_price_rule.yaml sample
opened by bartoszherba 1

Add rewrites

ubuntu@ubuntu-xenial:/var/www/magento2/dev/tests/integration$ phpunit --testsuite="magento2-configurator" --filter=testShouldCreateNewRewritesFromCsv
PHPUnit 4.1.0 by Sebastian Bergmann.

Configuration read from /var/www/magento2/dev/tests/integration/phpunit.xml.dist

URL Rewrite: "Redirect One" created
URL Rewrite: "Redirect Two" created
URL Rewrite: "Redirect Three" created
URL Rewrites Complete
.

Time: 23.51 seconds, Memory: 44.00MB

OK (1 test, 15 assertions)

=== Memory Usage System Stats ===
Memory usage (OS):	74.70M (169.78% of 44.00M reported by PHP)
Estimated memory leak:	30.70M (41.10% of used memory)

opened by ghost 1

Not compatible with PHP 8 due to dependencies

Whilst this module in itself doesn't specify any PHP requirements and the code is compatible with PHP 8, the dependency on "firegento/fastsimpleimport": "1.3.4" makes this module also not compatible. Firegento have resolved the PHP compatibility in version 2+ but the exact versioning used here makes it not possible to update that module individually.

Error: during bin/magento setup:di:compile

Resolution: modify the composer requirement for firegento/fastsimpleimport to either not specify a version, or so that version 2+ can be installed

opened by NathanDayFE 0
Not able to add multiple store on same website

Magento version EE 2.3.5 Module version 3.3.1

I am trying to add website and multiple store on same website. But Its showing error Group with the same code already exists.

Also for newly created website, New store added Configurator's Website Store USA but store code is missing.

Attached the websites. websites-yaml.txt yaml file

Could you please guide if anything wrong in yaml file.

opened by dhirajdanodeborn 2
Run Configurator Without a master.yaml

Create a new option to run Configurator without needing a master.yaml file. The option should accept a location to look for the files. The files in the directory will need to be structured in a specific way to identify the component e.g. pages runs the CMS pages component.

opened by paulpartington-cti 0
Export functionality

Any chance of getting some export functionality to generate the data YAML files automatically?

Like in existing systems with 300 attributes I could just run configurator:export attributes which generates the attributes.yaml file with all current data, which I can then easily edit later on.

One could even create data by hand in Magento backend and create the YAML files afterwards to store in vcs.

opened by Morgy93 0

Releases(3.1.4)

3.1.4(May 30, 2022)
Bring in the latest version of firegento/fastsimpleimport

Documentation fix (thanks @frqnck)

Source code(tar.gz)
Source code(zip)
3.1.3(Jan 14, 2021)
Enhances the detection of the file type with remote sources

Improves the product import by running the data through the validator and removing any failing products

Source code(tar.gz)
Source code(zip)
3.1.2(Oct 21, 2020)
Adds feature to auto-encrypt any configurations using the Encrypted back-end model, even is the encryption flag isn't stated in the YAML. encryption can still be manually used to properties with non-existent/different backend models as appropriate.

Source code(tar.gz)
Source code(zip)
3.1.1(May 5, 2020)

Source code(tar.gz)
Source code(zip)
v3.1.0(Mar 2, 2020)

New sequence component allowing you to define sales sequences for sequences that have not been created.
Source code(tar.gz)
Source code(zip)
v3.0.1(Feb 7, 2020)

Fixes a few bug with the catalog price rules importer. First of all, it had a completely irrelevant class being used as a processor which was never going to work. This is sorted now. Sorry!

We also noticed some issues with this component when installing on 2.3.4 which we've fixed.
Source code(tar.gz)
Source code(zip)
v3.0.0(Jan 20, 2020)
Configurator 3.0.0 is here and is threatening to break down Magento walls like the Kool-Aid man. If you have any custom components, you'll need to refactor them to use the ComponentInterface. Check out the highlights below.

No more object manager to load components. Components are now loaded using di.xml

Each component is now a standalone class and implements the ComponentInterface.

As a component no longer extends from a specific parser (e.g. CSV) your source can now be in any one of CSV, YAML, or JSON.

Sources can be loaded from a remote URL

You can pass in the --ignore-missing-files (-i) flag into configurator:run to ensure that missing files are skipped #84

Fixed #93

Source code(tar.gz)
Source code(zip)
v2.0.4(Jan 31, 2019)

Fix a warning on the products when trying to call count() on class members with no value.
Source code(tar.gz)
Source code(zip)
v2.0.3(Jan 31, 2019)

Updates the dependency for symfony/yaml to match Magento 2.2 and 2.3
Source code(tar.gz)
Source code(zip)
v2.0.0(Oct 17, 2018)
Magento 2.2 Support

Due to dependancy issues between symfony/yaml and symfony/console in Magento 2.2, you may have to include the following version of the packages.

composer require symfony/config:4.1.* composer require symfony/dependency-injection:3.3.*

Bug Fixes and Updates

Attribute Set Code Fix

Codesniffer Updates

PHP Unit 6.2 support

Store configuration encrypted values

Tiered Pricing Import Component

master.yaml global source is now optional if you include environment specific sources

Sample file updates

Source code(tar.gz)
Source code(zip)
v1.4.1(Mar 6, 2018)

Customer attributes component supports used_in_forms. Fixed bug when trying to save values to created customer attributes via data import (such as the customer component).
Source code(tar.gz)
Source code(zip)
v1.4.0(Feb 5, 2018)

New customer attributes component. Slightly refactored attributes component.
Source code(tar.gz)
Source code(zip)
v1.3.0(Jan 31, 2018)
Shipping Table Rates addition

Thanks @alexbiddle
Source code(tar.gz)
Source code(zip)
v1.2.0(Jan 26, 2018)
Catalog Price Rules Component

Additional Attribute Mappings

Source code(tar.gz)
Source code(zip)
v1.1.0(Jan 22, 2018)
New SQL Component

Simplified attribute config map

Tax rules & classes fix on multiple rates

Product description & short description parse update for non-html text from CSV.

Source code(tar.gz)
Source code(zip)
v1.0.0(Nov 11, 2017)

Version 1! Big thanks to the MageTitans Community
Source code(tar.gz)
Source code(zip)
v0.21.1(Sep 20, 2017)
Fix bug where environment sources were not parsed - https://github.com/ctidigital/magento2-configurator/pull/41 . Thanks @thaddeusmt!

Fix the PHP requirements to work with Magento 2.2 - https://github.com/ctidigital/magento2-configurator/pull/42. Thanks @dcole-inviqa!

Add validation when importing the customer to make sure all the columns have been specified.

Source code(tar.gz)
Source code(zip)
v0.21.0(Aug 8, 2017)

Create a customer import component. The component allows both customers and addresses to be imported using a single CSV file.
Source code(tar.gz)
Source code(zip)
0.20.0(Jul 31, 2017)

Update the Firegento_FastSimpleImport extension to 1.1.0. Improve the image handling so that it doesn't resave the image if it already exists and add some image validation Create attribute options automatically when required by the import. Split out the image and attribute option logic into their own files.
Source code(tar.gz)
Source code(zip)
v0.19.1(Jul 20, 2017)

Just a Travis CI improvement
Source code(tar.gz)
Source code(zip)
v0.19.0(Jul 14, 2017)
New Product Links component

Related Products

Up-Sell Products

Cross-Sell Products

Source code(tar.gz)
Source code(zip)
v0.18.0(Jun 29, 2017)

Allows the theme to be set using the full path of the theme rather than the ID.
Source code(tar.gz)
Source code(zip)
v0.17.1(Jun 29, 2017)

Get the review entity ID rather than hardcoding it as 1.
Source code(tar.gz)
Source code(zip)
v0.17.0(Jun 16, 2017)

Add review ratings.
Source code(tar.gz)
Source code(zip)
v0.16.0(Jun 9, 2017)

Addition of the rewrites component.

Thank You @furan917 & @alexbiddle
Source code(tar.gz)
Source code(zip)
v0.15.3(Jun 9, 2017)
Added CLI Logging onto attribute sets

Changing the order attribute sets execution.

Source code(tar.gz)
Source code(zip)
v0.15.2(May 16, 2017)

Add the setup class as a virtual type so that it can be used after compilation.
Source code(tar.gz)
Source code(zip)
v0.15.1(May 3, 2017)

Update the checks for attribute keys.
Source code(tar.gz)
Source code(zip)
v0.15.0(Apr 27, 2017)

Allow product images to be specified using a remote URL. The images will be downloaded as part of the import.
Source code(tar.gz)
Source code(zip)
v0.14.2(Apr 21, 2017)

Composer bump (same as v0.14.1)
Source code(tar.gz)
Source code(zip)