User story #7377
closed
Adapt rudderify script to use <FILE> in the generated metadata.xml
Added by Nicolas CHARLES about 9 years ago.
Updated over 2 years ago.
Description
To allow for better isolation of promises, adapt the rudderify script to add a new FILE entry with the cfengine promise file in the metadata.xml
- Related to User story #7376: Authorize both path relative to technique and to config-repos in technique metadata.xml descriptor added
- Related to deleted (User story #7376: Authorize both path relative to technique and to config-repos in technique metadata.xml descriptor)
- Related to User story #7402: Add a <FILE> tag in metadata.xml to allow simple file copy into techniques added
- Subject changed from Adapt rudderify script to use absolute path in the generated metadata.xml to Adapt rudderify script to use <FILE> in the generated metadata.xml
- Description updated (diff)
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/ncf/pull/263
Please update the technique to make use of a RUDDER_CONFIGURATION_REPOSITORY root, as described in #7402
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset commit:98b8fa93a72a0f37d571e7d983135ab179cbd6b1.
Applied in changeset commit:b5b9c556939671d96b079348d20d2514214a624c.
Ha, the file is not added in the inputs list :(
- Status changed from Pending release to Released
- Target version changed from master to ncf-1.2
- Project changed from 41 to Rudder
- Category set to Generic methods
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by