Bug #7429: Files added with the <FILE> tag in rudderify are not included in the input list - Rudder - Issue Tracker

Actions

Copy link

Bug #7429

closed

User story #7402: Add a <FILE> tag in metadata.xml to allow simple file copy into techniques

Files added with the <FILE> tag in rudderify are not included in the input list

Added by Nicolas CHARLES about 9 years ago. Updated about 9 years ago.

Status:

Released

Priority:

1 (highest)

Assignee:

François ARMAND

Category:

Techniques

Target version:

3.2.0~beta1

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

When changed from "include all" to "include specific files" in parent tickets
however, there is nothing to actually tell we need to include the file in the input list, resulting in an unused dandling file :(

Actions

Copy link

Updated by Jonathan CLARKE about 9 years ago

Nicolas CHARLES wrote:

When changed from "include all" to "include specific files" in parent tickets
however, there is nothing to actually tell we need to include the file in the input list, resulting in an unused dandling file :(

I understand this is not what we want 100% of the time, but in some cases it is exactly what we want - for example, when using a template file in a Technique, that will be explicitly called from CFEngine policy, we don't want it in the CFEngine inputs.

So, an option would be ideal, indeed.

Actions

Copy link