The default behaviour of deploy is to check for broken dependencies when restoring or transferring content. So if for example a media picker on a content item references media that is either deleted or in the recycle bin in the other environment, the deploy operation will halt and a list of errors to be fixed displayed.
The behaviour can by changed by configuring: deploy ignoreBrokenDependencies="true" />, with which broken dependencies will be ignored.
It would be better to allow to ignore not just for all operations, but only for restore or transfer operations (as whilst it's quite likely you would want to not ignore problems reporting when transferring content to an upstream environment, you may not care so much when restoring to a lower one.
So we'd like to look at extending the configuration to support this.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4