ReverseDeploy and Delete from SOURCE?

Is it possible to have OD do a reverse deploy and then delete the SOURCE files? I know I can do this with a run-after script, but then I have to maintain the run-after script on several servers, keeping the list of stuff-to-delete up to date.

It would be great if I could drive the whole process from a single OD configuration.

My other thought was to do my reverse deploy, followed immediately by a forward deploy of an empty directory to each target...but that feels terribly hokey.

Ideas?

Find more posts tagged with

Comments

Adam Stoller

If I understand you correctly - no - you'd have to use either the DNR or null-deployment option you mentioned.

However - I'm curious. What exactly is the reason for wanting to delete the files from the source location after deploying them to the target location?

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

I am pulling user-generated data from our production web servers back into a "safe" location on an internal server. I don't want to leave user submitted information out on the public boxes any longer than I have to.

I was hoping there would be a way to do this with OD so that I could make the process transactional, minimizing the risk of losing data between the time the reverse deploy completes and the run-after script executes to delete the files.

Adam Stoller

Have your DNR script read the internal XML log from STDIN and use that information to determine what files to delete from the source area.

Note: in 5.6 - OpenDeploy generates manifest files - this might be easier to parse for you than the in-memory XML logs (though I never found the latter to be that difficult when using IWODHOME/solutions/perl/IWXML.pm)

--fish
(Interwoven Senior Technical Consultant)

Edited by ghoti on 01/31/03 05:53 AM (server time).