Rudder

I'm not sure what/where to correct that. On the one hand, it seems that the agent should send back the actual value. On the other hand, we are already doing a match on Rudder side between the value we saved as "expected" and the actual agent value, with for ex. variable replaced agent side.

Actually, what we really want is a report id, unique at component value level (with added rules to know if the value actually matches, and the mutliplicity of the reports in the case of a list being processed agent side).

So I propose to add a matching rule in Rudder server for `${const.dollar} == $`

There is something strange with "\" matching in the corresponding code.

In fact, the problem is not with the escape of ${const.dollar}, but with the incorrect escape of regex chars in the value. So () is interpreted as regex char, and are not used in the matches. We need to correctly escape them.

The "\" thing was most likely to avoid having "\x" sequence being interpreted as a regex character classes. It was not sufficient at all to avoid problems, and it is not necessary anymore with correct quotation.