I'm a little confused about the use of the doDeletes flag in OD configurations.
I have doDeletes set to no post a recovery situation. We were able to designate deleted files for submission using a workflow that calls an OD configuration that has doDeletes flag set to no and we verified that the files that did not exist (due to deletion) on the source were in fact deleted from the target.
Within the past few days I have gotten reports that the target files are now not getting deleted.
My questions:
1. Does doDeletes need to be set to yes to have files that have been deleted off of the source and submitted for deletion via a filelist deployment workflow deleted off of the target?
2. Will having doDeletes set to yes potentially delete files off of the target that are no longer on the source even if they are not specifically added to a filelist deployment?
See quotes from the documentation below.
File list deployments support the use of the doDeletes option. Those files that you want
to be deleted at the target must be named in the deployment file list file, and must not be
present in the source file location of the deployment. See “Transfer Rules” on page 132
for more information on the use of the doDeletes option. |
doDeletes — indicate whether (yes) or not (no) files and directories that reside in
the target file location but not in the source file location should be deleted following
the deployment. By default they are not. Default value is no. |
If the filter exists only on the source side, OpenDeploy ignores those excluded
source-side files and cannot deploy them. If the doDeletes feature is enabled, those
excluded source-side files that are also present on the target-side will be deleted. |
