BUGFIX: Finalise and deprecate site creation module for Neos 9.0 #5440
+95
−49
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves: #4719
In #5139 i removed the capabilities to create composer packages via web request which is now obsolete as we have the new CLI / Web setup: #4243
Now we can also reimplement 'import site' based on new SiteImportService from #5307 - the thing is this comes with some limitations like in use with CLI:
as proposed here Discussion improve site entity and site node relation #4470 (comment) the site must have a field to define the contentRepositoryId. In the current state we can only know via the to be created site name plus the site configuration in
Neos.Neos.sites
via its name or the fallback*
which is the 'destined' content repository.a current limitation of the setup is that it can really only be executed once. After the events are set deleting the site (soft, without pruning the cr) a reimport would just duplicate the events again which is not the desired step probably. For that we allow to prune the site via
flow cr:pruneAll
. Those steps are to be used with care and not available via GUI.The advantage CLI gives us is that for example failures in the done replay and all other steps are not obscured and can easily be be debugged. Also for managing multiple content repositories or changing dimensions configuration changes have to be undertaken which is closer to CLI.
Upgrade instructions
Review instructions
Checklist
FEATURE|TASK|BUGFIX
!!!
and have upgrade-instructions