https://issues.rudder.io/https://issues.rudder.io/themes/rudder7/favicon/favicon.ico?17096450182019-09-04T15:47:40ZIssue TrackerRudder - Bug #15640: Built in File Content technique does not warn about using cfengine variable syntax in file contenthttps://issues.rudder.io/issues/15640?journal_id=1143362019-09-04T15:47:40ZJanos Mattyasovszky
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-16 priority-default closed parent" href="/issues/15167">Bug #15167</a>: Invalid detection of empty strings for edition in Techniques</i> added</li></ul> Rudder - Bug #15640: Built in File Content technique does not warn about using cfengine variable syntax in file contenthttps://issues.rudder.io/issues/15640?journal_id=1148822019-09-16T10:27:34ZFrançois ARMANDfrancois.armand@rudder.io
<ul><li><strong>Target version</strong> set to <i>5.0.14</i></li></ul> Rudder - Bug #15640: Built in File Content technique does not warn about using cfengine variable syntax in file contenthttps://issues.rudder.io/issues/15640?journal_id=1154522019-10-03T14:36:01ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>5.0.14</i> to <i>5.0.15</i></li></ul> Rudder - Bug #15640: Built in File Content technique does not warn about using cfengine variable syntax in file contenthttps://issues.rudder.io/issues/15640?journal_id=1159472019-10-07T13:11:01ZFrançois ARMANDfrancois.armand@rudder.io
<ul><li><strong>Assignee</strong> set to <i>Nicolas CHARLES</i></li><li><strong>Priority</strong> changed from <i>70</i> to <i>69</i></li></ul><p>Adding in the field documentation the warning is easy, and we should defenitly do that. Having a real-time warning based on the input text is not possible right now (we don't know on rudder what are the defined variables on nodes). We could rule out some inputs, thought (like "no . in the variable name").</p>
<p>So for now, step 1: add warning in field documentation.</p> Rudder - Bug #15640: Built in File Content technique does not warn about using cfengine variable syntax in file contenthttps://issues.rudder.io/issues/15640?journal_id=1194362019-12-04T13:12:11ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>5.0.15</i> to <i>5.0.16</i></li><li><strong>Priority</strong> changed from <i>69</i> to <i>67</i></li></ul> Rudder - Bug #15640: Built in File Content technique does not warn about using cfengine variable syntax in file contenthttps://issues.rudder.io/issues/15640?journal_id=1220082020-02-13T16:03:55ZAlexis Moussetalexis.mousset@rudder.io
<ul><li><strong>Target version</strong> changed from <i>5.0.16</i> to <i>5.0.17</i></li><li><strong>Priority</strong> changed from <i>67</i> to <i>65</i></li></ul> Rudder - Bug #15640: Built in File Content technique does not warn about using cfengine variable syntax in file contenthttps://issues.rudder.io/issues/15640?journal_id=1254772020-04-16T21:52:56ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>5.0.17</i> to <i>5.0.18</i></li><li><strong>Priority</strong> changed from <i>65</i> to <i>63</i></li></ul> Rudder - Bug #15640: Built in File Content technique does not warn about using cfengine variable syntax in file contenthttps://issues.rudder.io/issues/15640?journal_id=1317122020-07-22T22:01:30ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>5.0.18</i> to <i>5.0.19</i></li><li><strong>Priority</strong> changed from <i>63</i> to <i>59</i></li></ul> Rudder - Bug #15640: Built in File Content technique does not warn about using cfengine variable syntax in file contenthttps://issues.rudder.io/issues/15640?journal_id=1325132020-08-13T11:49:41ZNicolas CHARLESnicolas.charles@rudder.io
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In progress</i></li></ul> Rudder - Bug #15640: Built in File Content technique does not warn about using cfengine variable syntax in file contenthttps://issues.rudder.io/issues/15640?journal_id=1325142020-08-13T12:11:41ZNicolas CHARLESnicolas.charles@rudder.io
<ul></ul><p>Only does Line replacement regular expressions fail in my test</p> Rudder - Bug #15640: Built in File Content technique does not warn about using cfengine variable syntax in file contenthttps://issues.rudder.io/issues/15640?journal_id=1325152020-08-13T12:29:35ZNicolas CHARLESnicolas.charles@rudder.io
<ul><li><strong>Status</strong> changed from <i>In progress</i> to <i>Rejected</i></li></ul><p>Tested on 5.0.17: agent can insert any variable ${} , delete using ${}, replace using ${} without any escaping</p>
<p>I'm rejecting it, feel free to reopen it if you have a use case where it fails</p>