Project

General

Profile

Actions

Bug #13887

closed

Option description for "File download (Rudder server)" technique is misleading

Added by François ARMAND over 5 years ago. Updated over 5 years ago.

Status:
Released
Priority:
N/A
Category:
Techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

'File download (Rudder server)' technique lets you copy things from `/var/rudder/configuration-repository/shared-files/` to somewhere else.

You have three option to choose what to copy:

- Only this file
- The whole content of the folder
- The folder, its content, and all the subfolders

What I undestand, if I have:

.../configuration-repository/shared-files/
└── dir
    ├── dir2
    │   └── foo.txt
    └── hollymolly.txt

And that I set "dir" in source path, "/tmp" in destination path, is that the content will be:

- Only this file

/tmp/
└── dir/

But it actually does nothing.

- The whole content of the folder

/tmp/
├── dir2 (empty)
└── hollymolly.txt

And it's that!

- The folder, its content, and all the subfolders

/tmp/
└── dir
    ├── dir2
    │   └── foo.txt
    └── hollymolly.txt

But it actually skips "dir" (only content is copied)

Moreover, folder is used a couple of time, when `directory` is used in (many more) other places.

Change into:

- Only this file (or nothing for a directory)
- The direct content of the directory (one level)
- The whole content of the directory (recursively)

(and: Apply the sticky bit to the whole folder? (caution, use with care) => Apply the sticky bit to the whole directory? (caution, use with care)

(even so, that does not seems very consistent. Why the sub-directory is created in second case if skipped in the first? But it can be ok)


Subtasks 1 (0 open1 closed)

Bug #13888: Option description for "dowload for shared files" is mileading and mixed use of folder/directory (rudder 4.3)RejectedFrançois ARMANDActions
Actions

Also available in: Atom PDF