Skip to content

Releases: kaliop-uk/ezmigrationbundle

5.11.0

30 Jun 11:44
Compare
Choose a tag to compare
  • New: new constraints isnull and notnull are now supported in 'if' clauses to match references values

  • New: the migration_definition/generate step now supports an 'if' clause

  • New: the migration_definition/generate step now supports setting a reference to the whole definition

  • New migration step: migration_definition/save. Useful in content migrations / syndication scenarios

  • BC changes: the migration_definition/generate step now uses a different syntax for setting references. The old one is still accepted but deprecated (key json_path has been replaced by attribute)

5.10.2

18 Apr 12:23
Compare
Choose a tag to compare
  • Fixed issue #232: error with EmbeddedRegexpReferenceResolverTrait.php and php 7.4

  • Improved: massively reworked travis setup to make it friendlier to ezplatform 3 installations

5.10.1

01 Aug 08:28
Compare
Choose a tag to compare
  • Fix issue #216: cannot update a location's parent matching it by remote id

  • Improved: when creating/updating content, allow to set references to location_remote_id

  • Improved: add plumbing to allow future usage of custom content types for UserGroups

5.10.0

15 Jul 10:29
Compare
Choose a tag to compare
  • Fix issue #210: cannot match locations by group

  • Fix: matching users by usergroup_id

  • Fix: file migration steps would not work when using an if element

  • Fix issue #207: java.lang.NegativeArraySizeException error when using SOLR multi core

  • Improved the DSL docs for the management of Roles (see issue #211)

  • Implemented request #205: allow to generate migrations for tag creation independently of content

  • Implemented request #215: better error message when migrations fail because an invalid admin account is used to run them

  • Implemented request #211: allow to unassign roles from groups on update

  • Allow more flexibility in tag matching:

    • allow to match all tags
    • when specifying a parent-tag id, the remote_id can be used in its place
  • Implemented request #204: an event of class MigrationGeneratedEvent is now emitted when a migration definition is generated via the command kaliop:migration:generate, allowing developers to easily customize the generated migrations

  • Improved: it is now possible to set a reference to the remote_id of any created/updated/deleted userGroup

  • Added a Docker-Compose based stack to ease execution of the test suite locally. See the main README for details on use

5.9.5

01 Jul 08:21
Compare
Choose a tag to compare

Fix issue: usergroup_id matching for users was not working.

5.9.4

18 May 09:32
Compare
Choose a tag to compare

Fix issue #202: RoleManager::createLimitation fails when using array reference

5.9.3

16 Apr 10:28
Compare
Choose a tag to compare

(note: all changes since 5.9.0 listed here)

  • Fixed: match 'all' languages would raise an exception

  • Fixed: the migrate command terminates with non-0 exit code when any migration failed, even if it is given the -i option

  • Fixed: the mass_migrate command terminates with non-0 exit code when any migration or subprocess failed

  • Improved: when migrations fail, the error message is written to stderr instead of stdout, for both the migrate and mass_migrate commands

  • Improved: better error output by the migrate and mass_migrate commands. In particular:

    • they now report the number of non-executed migrations besides the failed and skipped ones.
    • the error output when using the -p option has been made more similar to the one of the standard case
  • Improved: better support for -v and -q options for the migrate and mass_migrate commands, esp. when used together with -p

  • New: the migrate and mass_migrate commands accept an option survive-disconnected-tty. This helps in cases where you would normally run the migrations using screen or tmux, such as over ssh connections which risk being dropped before the migrations have finished executing

  • New: the migrate and mass_migrate commands accept an option force-sigchild-enabled. This is useful when you are running on eg. Debian and Ubuntu linux, and run the migrations using separate subprocesses: in such scenario there are chances that migrations will be reported as having failed executing even though they have not. Using the force-sigchild-handling option should fix that. For reference, see comment 12 in this ticket: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/516061

  • BC changes:

    • code which relies on parsing the output and/or exit code of migrate and mass_migrate commands should be adjusted

5.9.2 - please do not use

15 Apr 09:18
Compare
Choose a tag to compare

Use 5.9.3 or later instead

5.9.1 - please do not use

12 Apr 16:40
Compare
Choose a tag to compare

Use 5.9.3 or later instead

5.9.0

11 Apr 08:21
Compare
Choose a tag to compare
  • New: the role/create migration step now resolves references for role names. Same for role/update.

  • New: new migration steps language\update, language\load, section\load, role\load, object_state\load, object_state_group\load

  • New: more flexible matching for migration step language\delete

  • New: more reference resolving in section creation and update

  • New: the generate command now has a --list-types option that will have it list all migration types available for generation

  • Fix: warnings generated when creating array-valued refs using an empty collection of items

  • Fix: references would not be resolved for Author and Selection fields, when the field value is given in array form.
    Ex: this will now be resolved

      ...
      attributes:
          country: # an ezselection field
              - italy
              - reference:mycountry
    
  • BC changes:

    • the language\delete step should not be used any more with a lang element, but with match instead