Details
-
Feature
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
Current Situation
- Pre-Processing occurs on the following events:
- CommandBeforeFile
- Processing is performed for target files that can be written.
- Processing is dropped in case of skipped transfers
- e.g. in case that existing should not be overwritten
- DisableOverwriteFiles (mapping overwrite_files=false)
- e.g. in case that existing should not be overwritten
- Processing is performed for the first file in case of failed transfers
- e.g. if target folders do not exist
- CommandBeforeOperation
- Processing is performed in any situation
- CommandBeforeFile
- Post-Processing occurs on the following events:
- CommandAfterFile Event
- Processing is performed in case of skipped transfers
- Processing is dropped in case of failed transfers
- CommandAfterOperation Event
- Processing is performed in case of skipped transfers
- Processing is dropped in case of failed transfers
- e.g. if target folders do not exist
- CommandAfterFile Event
DesiredBehavior
- Users would want to control in which situation pre- and post-processing scripts should be executed.
- Pre-Processing
- CommandBeforeFile
- Attribute: enable_for_skipped_transfer.
- The default value is false which corresponds to the behavior with previous releases.
- Mapping: pre_command_enable_for_skipped_transfer
- Attribute: enable_for_skipped_transfer.
- CommandBeforeFile
- Post-Processing
- CommandAfterFile
- Attribute: disable_for_skipped_transfer.
- The default value is false which corresponds to the behavior with previous releases.
- Mapping: post_command_disable_for_skipped_transfer
- Attribute: disable_for_skipped_transfer.
- Environment variables in the SFTPPostProcessing and LocalPostProcessing:
- YADE_FILE_TRANSFER_STATUS
- possible values: transferUndefined, waiting4transfer, transferring, transferInProgress, transferred, transfer_skipped, transfer_has_errors, transfer_aborted, compressed, notOverwritten, deleted, renamed, ignoredDueToZerobyteConstraint, setBack, polling
- YADE_FILE_IS_TRANSFERRED
- possible values: 0 or 1
- YADE_FILE_TRANSFER_STATUS
- CommandAfterFile
Configuration requirements
Attachments
Issue Links
- affects
-
YADE-510 Possibly NPE while reading profile with CommandBeforeFile or CommandAfterFile setting
- Released