Skip to content

Aligned configuration docs across versions for Deploy #6076

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.

Sign up for GitHub

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 1 commit into from
May 8, 2024
Merged

Aligned configuration docs across versions for Deploy #6076

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions 10/umbraco-deploy/getting-started/deploy-settings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ For illustration purposes, the following structure represents the full set of op
"Deploy": {
"Settings": {
"ApiKey": "<your API key here>",
"Edition": "Default",
"Edition": "Default",
"ExcludedEntityTypes": [],
"RelationTypes" : [],
"ValueConnectors": [],
Expand All @@ -52,7 +52,7 @@ For illustration purposes, the following structure represents the full set of op
"IgnoreBrokenDependenciesBehavior": "Restore",
"AcceptInvalidCertificates": false,
"TransferFormsAsContent": true,
"TransferDictionaryAsContent": false,
"TransferDictionaryAsContent": false,
"SetEmptyDictionaryItemsOnTransfer": true,
"IgnoreMissingLanguagesForDictionaryItems": false,
"AllowMembersDeploymentOperations": "None",
Expand Down
2 changes: 1 addition & 1 deletion 12/umbraco-deploy/getting-started/deploy-settings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ For illustration purposes, the following structure represents the full set of op
"Settings": {
"ApiKey": "<your API key here>",
"ApiSecret": "<your API secret here>",
"Edition": "Default",
"Edition": "Default",
"ExcludedEntityTypes": [],
"RelationTypes" : [],
"ValueConnectors": [],
Expand Down
9 changes: 9 additions & 0 deletions 13/umbraco-deploy/getting-started/deploy-settings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,7 @@ For illustration purposes, the following structure represents the full set of op
"NumberOfSignaturesToUseAllRelationCache": 100,
"ContinueOnMediaFilePathTooLongException": false,
"SuppressCacheRefresherNotifications": false,
"ResolveUserInTargetEnvironment": false,
"Suspensions": {
"DiskRead": "All",
"PartialRestore": "All",
Expand Down Expand Up @@ -380,6 +381,14 @@ In production this setting shouldn't be changed from it's default value of `fals

If attempting a one-off, large transfer operation, before a site is live, you could set this value to `true`. That would omit the firing and handling of these notifications and remove their performance overhead. Following which you would need to ensure to rebuild the cache and search index manually via the backoffice _Settings_ dashboards.

## ResolveUserInTargetEnvironment

With this setting assigned a value of `true`, Umbraco Deploy will attempt to resolve users when transfers are made to new environments.

Users and user groups are maintained separately in different environments, so it isn't always the case that an editor has accounts across all environments. When an account exists matching by email address, Deploy will associate the changes made in upstream environments with the user that initiated the transfer. Allowing the expected information about save and publish operations to be available in the audit log of the environment where the data was transferred.

When the setting is set to `false`, or a matching account isn't found, the audit records will be associated with the super-user administrator account.

### Suspensions

Deploy operations suspend scheduled publishing, Examine indexing, document cache and/or signature database update events by default. You can amend this behavior for all supported or specific operations using these settings.
Expand Down