File List deployment with deleted folders/files

Johnny

OD 6.0.1

We use file list type profiles for all workflow deployments. Nothing new there, it gives us a nice standard way to push only those changes that are attached to the workflow including deleted folders and files.

We are having one problem though.

if an existing folder (not deleted) is attached that may contain some deleted files/folders somewhere beneath, those deleted files/folders are not removed.

Would that not be expected behavior of a file list considering all the other cases where it does work.

It can:
- publish a file explicitly listed in the file list.
- remove a deleted file explicitly listed in the file list.
- recursively publish all existing files/folders of folder attached to the file list.

It does not :
- recursively remove any deleted files/folders that may exist in a folder attached to the file list.

So how does OD handle that without creating a separate exception process. Area comparison is not practical just to catch this one use case.
So far I can only thing of having to rewrite our deployment step to first compare the file list against staging and explicitly attach all the deleted files to the deployment/workflow. This certainly seems like a workaround.

Have I missed something? Are we looking at a bug? - I don't get how this exception is seen as intended behavior considering what it does support correctly. Maybe I've set it up wrong?

Thoughts?


John Cuiuli

Migrateduser

John,

There is a feature request open for this behavior #64444. Another customer has asked for this as well.

So currently, the files have to be explicitly listed in order to get deleted. I know that in our ControlHub module, our OOTB workflow uses
"iwlistmod” to get the list of all modified files/dirs, and attaches them all to the job. So if you don't mind having *everything* that's modified in the workarea getting attached to the job, you could do the same thing.

Mariam