Bug #11862
closed
Architecture #10625: Don't merge directive from same technique on generation
RudderUniqueID is not replaced when used in OUTPATH
Added by Nicolas CHARLES almost 7 years ago.
Updated over 6 years ago.
Category:
Web - Config management
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Very Small
Description
With the following code in the metadata.xml
<TMLS>
<TML name="filesPermissions"/>
<TML name="permlist">
<INCLUDED>false</INCLUDED>
<OUTPATH>filesPermissions/RudderUniqueID/permlist</OUTPATH>
</TML>
</TMLS>
i get the following paths
.
├── 2.1_84a1104f_1164_4e74_bb4b_7f1552005ea5
│ └── filesPermissions.cf
└── RudderUniqueID
└── permlist
I was expecting RudderUniqueID to be replaced
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Effort required set to Very Small
- Priority changed from 0 to 80
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/1835
- Status changed from Pending technical review to Pending release
- Parent task set to #10625
- Priority changed from 80 to 79
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.0~beta1 which was released today.
- Priority changed from 79 to 77
I still have this issue:
/var/rudder/cfengine-community/inputs/filesPermissions# tree
.
├── 2.2_04f409ae_fa6e_4495_85d4_594cc5eb1533
│ └── filesPermissions.cf
└── RudderUniqueID
└── permlist
2 directories, 2 files
- Related to Bug #12344: RudderUniqueId is not replaced when using OUTPATH in metadata, causing no report in File Permissions added
Also available in: Atom
PDF