search

OXIDprojects / oxid_modules_config

OXID Module Configuration Im-/Exporter module by OXID Professional Services
GNU General Public License v3.0
3 stars 9 forks source link

Feature generate oxserial after import #32

Closed alfredbez closed 5 years ago

alfredbez commented 5 years ago

There are two fields related to the serial in the config-export at the moment:

  1. aSerials in the oxconfig table, which holds multiple license keys which you can also enter in the OXID backend
  2. OXSERIAL in the oxshops table, which is generated after you enter the aSerials in the OXID backend

The current workflow to add new license keys is:

  1. Add license keys manually in OXID backend
  2. Create new config export
  3. Add related changes to git

Sometimes we want to add the license key directly into the yaml file and roll that change out without opening the OXID backend. Therefore we need a mechanism to generate the OXSERIAL inside the config:import command.

I fixed some non-related stuff (whitespace and a variable-name), to get only the related diff take a look at this commit: https://github.com/OXIDprojects/oxid_modules_config/commit/11f4c3335804da7d2210b87f4cea3f2281ae513f

You can test this already by using "oxid-professional-services/oxid-modules-config": "dev-feature-generate-oxserial-after-import" in your composer.json or directly by calling:

composer require oxid-professional-services/oxid-modules-config dev-feature-generate-oxserial-after-import