Project

General

Profile

Actions

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 over 6 years ago. Updated about 6 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Very Small
Priority:
77
Name check:
Fix check:
Regression:

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


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #12344: RudderUniqueId is not replaced when using OUTPATH in metadata, causing no report in File PermissionsReleasedNicolas CHARLESActions
Actions

Also available in: Atom PDF