Skip to content

FEATURE: "Legacy" nodedata export/import #3810

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 11 commits into from
Aug 8, 2022
Merged

Conversation

bwaidelich
Copy link
Member

@bwaidelich bwaidelich commented May 27, 2022

Reworks the contentrepositorymigrate:run command such that it uses the
new Neos.ContentRepository.Export package to export nodes from the neos_contentrepository_domain_model_nodedata of the
current database or any other to the event sourced content repository.

Usage

Interactively

./flow contentrepositorymigrate:run

Pre-configured

./flow contentrepositorymigrate:run --config '{"dbal": {"dbname": "some-other-db"}, "resourcesPath": "/some/other/project/Data/Persistent/Resources"}'

(optionally with --verbose flag)

Resolves: #3795

Reworks the `contentrepositorymigrate:run` command such that it uses the
`Neos.ESCR.Export` package (to be renamed to `Neos.ContentRepository.ImportExport`)
to export nodes from the `neos_contentrepository_domain_model_nodedata` of the
current database or any other to the event sourced content repository.
@bwaidelich
Copy link
Member Author

bwaidelich commented May 27, 2022

This works basically, but there are still some todos:

  • Support variants with different parent nodes (in NeosLegacyEventMiddleware)
  • [ ] Respect succeedingNodeAggregateIdentifier for NodeAggregateWithNodeWasCreated events (in NeosLegacyEventMiddleware) this case should not be relevant
  • Assets are not yet exported
  • Import currently fails with Expected version: NO STREAM (-1), actual version: 0 – a nicer exception or a way to delete events would be better
  • No site is created automatically
  • [ ] Script to compare "old" and "new world" (plain text file with all nodes) (9.0: Tree Structure Comparison Tool #3853)

...explaining prioritization of specialization/generalization events
…ckage

## Usage

    ./ flow contentrepositorymigrate:run
* Remove `Neos.ESCR.Export` package
* Add `Neos.EventSourcing.Export` package as library (pure composer package)
* Move migration coordination to `Neos.ContentRepository.LegacyNodeMigration` package (for now)

## Usage

### Interactively:

    ./flow contentrepositorymigrate:run

### Preconfigured

    ./flow contentrepositorymigrate:run --config '{"dbal": {"dbname": "some-other-db"}, "resourcesPath": "/some/other/project/Data/Persistent/Resources"}' --verbose
@skurfuerst skurfuerst merged commit 6d2fdf1 into 9.0 Aug 8, 2022
@skurfuerst skurfuerst deleted the feature/legacy-export-import branch August 8, 2022 12:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants