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 almost 9 years ago.
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 :(
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.
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/969
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.2.0~beta1 which was released today.
Also available in: Atom
PDF