FEATURE: node migration kickstart command

[crydotsnake]

Review instructions

This pull request contains a new feature for the Neos.Kickstarter package. The new command is: ./flow kickstart:nodemigration. I can provide a $packageKey. The $packageKey is the respective site package. It also appends the current $timeStamp in the format: YmdHis to the generated migration.

Demo:

The node migration is displayed as usual when running: ./flow node:migrationstatus:

The created node migration comes also with a template, which can be customized directly. The template also contains information about the node migration part in the Neos documentation.

Template

#############################################################################################################################################################################
# For more information about node migrations in Neos, checkout the documentation: https://neos.readthedocs.io/en/stable/References/NodeMigrations.html?highlight=migrations #
#############################################################################################################################################################################
up:
  comments: 'Migration description'
  migration:
    -
      filters:
        -

down:
  comments: 'No down migration available'

Related information:

• FEATURE: Command for creating a node migration neos-development-collection#3881

Checklist

• Code follows the PSR-2 coding style
• The PR is created against the lowest maintained branch
• Reviewer - PR Title is brief but complete and starts with FEATURE|TASK|BUGFIX
• Reviewer - The first section explains the change briefly for change-logs
• Reviewer - Breaking Changes are marked wit !!! and have upgrade-instructions

[crydotsnake]

A little note about this change.

I had a discussion with @kitsunet about a problem that i had, while working on my ./flow kickstart:nodemigration feature. The problem was that the output in my generateNodeMigration() method looked like this:

Created .../Test20220906183945.yaml
Your node migration has been created successfully.

The full path to the file was missing. This was because the generateFile() method could only handle Resources, Tests and Classes. We refactored the generateFile() method so that it works the same as before. But now it also can handle the full path to a migration created with the ./flow kickstart:nodemigration command:

Created .../Sites/Neos.Demo/Migrations/ContentRepository/Test20220907193517.yaml
Your node migration has been created successfully.

[crydotsnake]

⚠️ This feature will be moved to the Neos.ContentRepository Package. (WIP) ⚠️

[kitsunet]

Closing as it needs to be done in another repository.