Add ValidateDependenciesOnImport documentation

Author: ronaldbarendse

13/umbraco-deploy/getting-started/deploy-settings.md

@@ -77,7 +77,8 @@ For illustration purposes, the following structure represents the full set of op
           "Export": "All"
         },
         "HideConfigurationDetails": false,
-        "HideVersionDetails": false
+        "HideVersionDetails": false,
+        "ValidateDependenciesOnImport": true
       },
       "ImportOnStartup": {
         "Enabled": true,
@@ -457,6 +458,15 @@ If set to `true` the configuration details shown on the setting's dashboard will
 
 If set to `true` the version details shown on the setting's dashboard will be hidden.
 
+### ValidateDependenciesOnImport
+
+A default notification handler for the `ValidateArtifactImportNotification` is registered by Deploy that:
+
+* Adds warnings for dependencies that must match exactly, and are both not in the import and not with matching checksums in the target environment
+* Adds warnings for all remaining content dependencies and errors for all schema dependencies that don't exist in the import
+
+To avoid this handler from being registered, you can set this setting to `false`.
+
 ### Import on startup
 
 Deploy can import content and/or schema previously exported from another Umbraco installation on start-up. This can be used to quickly setup a baseline/starter kit or as a workaround for large ZIP archives that can't be (easily) uploaded via the backoffice.

14/umbraco-deploy/getting-started/deploy-settings.md

@@ -78,7 +78,8 @@ For illustration purposes, the following structure represents the full set of op
           "Export": "All"
         },
         "HideConfigurationDetails": false,
-        "HideVersionDetails": false
+        "HideVersionDetails": false,
+        "ValidateDependenciesOnImport": true
       },
       "ImportOnStartup": {
         "Enabled": true,
@@ -464,6 +465,15 @@ If set to `true` the configuration details shown on the setting's dashboard will
 
 If set to `true` the version details shown on the setting's dashboard will be hidden.
 
+### ValidateDependenciesOnImport
+
+A default notification handler for the `ValidateArtifactImportNotification` is registered by Deploy that:
+
+* Adds warnings for dependencies that must match exactly, and are both not in the import and not with matching checksums in the target environment
+* Adds warnings for all remaining content dependencies and errors for all schema dependencies that don't exist in the import
+
+To avoid this handler from being registered, you can set this setting to `false`.
+
 ### Import on startup
 
 Deploy can import content and/or schema previously exported from another Umbraco installation on start-up. This can be used to quickly setup a baseline/starter kit or as a workaround for large ZIP archives that can't be (easily) uploaded via the backoffice.

15/umbraco-deploy/getting-started/deploy-settings.md

@@ -78,7 +78,8 @@ For illustration purposes, the following structure represents the full set of op
           "Export": "All"
         },
         "HideConfigurationDetails": false,
-        "HideVersionDetails": false
+        "HideVersionDetails": false,
+        "ValidateDependenciesOnImport": true
       },
       "ImportOnStartup": {
         "Enabled": true,
@@ -464,6 +465,15 @@ If set to `true` the configuration details shown on the setting's dashboard will
 
 If set to `true` the version details shown on the setting's dashboard will be hidden.
 
+### ValidateDependenciesOnImport
+
+A default notification handler for the `ValidateArtifactImportNotification` is registered by Deploy that:
+
+* Adds warnings for dependencies that must match exactly, and are both not in the import and not with matching checksums in the target environment
+* Adds warnings for all remaining content dependencies and errors for all schema dependencies that don't exist in the import
+
+To avoid this handler from being registered, you can set this setting to `false`.
+
 ### Import on startup
 
 Deploy can import content and/or schema previously exported from another Umbraco installation on start-up. This can be used to quickly setup a baseline/starter kit or as a workaround for large ZIP archives that can't be (easily) uploaded via the backoffice.