Project

General

Profile

Actions

Bug #13664

closed

Mustache templating in audit mode always considers destination compliant once it exists

Added by Alexis Mousset over 5 years ago. Updated over 5 years ago.

Status:
Released
Priority:
N/A
Category:
Agent
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Very Small
Priority:
104
Name check:
Fix check:
Regression:

Description

We should compare the content of the file with the rendered template when in audit mode (as we do in enforce mode, but without actual destination changes). This is what is done by file_from_string_mustache and file_from_template_jinja2.

It seems (tested with 5.0 on Ubuntu 16.04) that this is not the case and that the agent skips content comparison and defines classes based on file existence only, which breaks mustache templated-files auditing.


Subtasks 2 (0 open2 closed)

Bug #13736: Mustache templating in audit mode always considers destination compliant once it exists - 5.0 branchReleasedBenoît PECCATTEActions
Bug #13754: Broken agent build after mustache class fixesReleasedBenoît PECCATTEActions
Actions

Also available in: Atom PDF