You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we were to create an item if there's a new root, it would need to happen after content type updates, but before spaces. This is an issue since these operations are in the opposite order in the current implementation.
Screenshots
N/A
The text was updated successfully, but these errors were encountered:
you are right, this will not work, as the item is missing and the sync command does not sync items. I am unsure whether this fits the sync context because we have the migrate-content command. I will need to think about this a little because there might be a switch option that will at least create an empty item (no language variant). This would need to happen after the creation of all content types.
In the meantime, you can probably use a combination of sync and migrate-content commands. You can sync the content types and their dependencies first, then you can migrate the root content item and lastly, you can sync the spaces. I know this consists of three steps, however, you can write a script using the functions data-ops provides.
Brief bug description
When syncing a space that links a new web spotlight root, the operation fails since there is no matching item in the target environment.
Repro steps
"The referenced root item '{codename: root}' was not found. Provide a reference to an existing root item."
Expected behavior
Preferably I'd like to see the root item synced. However, I understand that this may not be in line with the expectations of the
sync
command.Test environment
[email protected]
Additional context
If we were to create an item if there's a new root, it would need to happen after content type updates, but before spaces. This is an issue since these operations are in the opposite order in the current implementation.
Screenshots
N/A
The text was updated successfully, but these errors were encountered: