If we Inject with the standard Inject tool and have it set to delete - can we have a disaster if:
1) the file does not exist
2) the path resolves to null
Scenarios may be
1) A signal from an MIS to archive a certain file - but that file was moved by a person or other system ahead of time
2) a bad input giving us path/to/file/null
My concern is from reading viewtopic.php?t=1497
ThanksWhile the stock Inject configurator is extremely powerful, for many operations, it poses a significant risk. The ability to copy and remove a remote file (which may be a variable) is extremely dangerous. The target variable could resolve incorrectly causing the destruction of Switch's own backing files, or other sensative files. In some cases, users have reported using the "Job repository" method of Inject, where "Job name" property resolves to null, which results in the entire repository being injected (and removed).