Request to enhance the Config Files → Copy step to preserve the original directory hierarchy when copying a directory, instead of flattening all files into a single destination path.
under review
F
Full Egret
When using the Config Files → Copy step with a directory path, the directory structure from the source is not retained at the destination. Instead, all files are flattened into a single target directory. This causes files with identical names to overwrite each other, resulting in loss of configuration data and unexpected behavior.
Example:
Source directory structure:
configs/
└── root/
├── env1/
│ └── env.properties
├── env2/
│ └── env.properties
├── env3/
│ └── env.properties
├── log4j2.xml
└── log4j2.txt
After using the Config Files copy step, the destination becomes:
env.properties (overwritten multiple times)
log4j2.xml
log4j2.txt
Since multiple env.properties files exist under different subdirectories, they overwrite each other in the destination directory. The original directory hierarchy (env1, env2, env3, etc.) is not preserved.
Log In
Sudarshan Purohit
marked this post as
under review