[PDB-3930] PQL's ~ matches incorrectly on dotted variables Created: 2018/06/02 Updated: 2018/09/13 Resolved: 2018/07/11
|Affects Version/s:||PDB 5.2.2|
|Reporter:||Daniel Parks||Assignee:||Rob Browning|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
The following query returns records:
|Method Found:||Needs Assessment|
|CS Frequency:||3 - 25-50% of Customers|
|CS Severity:||3 - Serious|
|CS Business Value:||4 - $$$$$|
|CS Impact:|| CS Triage feedback on this issue replicated from: PE-24298.
Although this does not affect classification, it would cause confusion in our customer base. It will lead to customers going down rabbit holes when attempting to debug classification issues which will lead to at least frustration if not a support call.
|Release Notes:||Bug Fix|
|Release Notes Summary:|| PuppetDB should no longer match regular expresions against fact values incorrectly. Previously (starting with 5.2.0) the "~" operator would end up trying to match the JSON-encoded representation of a fact value rather than the value itself. So, for example,
would fail when it should succeed, while
|QA Risk Assessment:||Needs Assessment|
The ~ operator treats dotted variables, e.g. parameters.ensure and facts.fqdn, as if their values were wrapped in double quotes.
Both of the following return thousands of records:
The following returns no records:
I initially reported this as
|Comment by Eric Thompson [ 2018/06/20 ]|
will this fix, implicitly, PE-24298?
edit: answering my own question: yes (according to Jon's investigation)
|Comment by Kenn Hussey [ 2018/06/21 ]|
|Comment by Maggie Dreyer [ 2018/06/21 ]|
I think for the time being Rob Browning is handling PDB prioritization, until he tells the rest of the team that he needs help. For the time being it sounded like he and Zak had a handle on it. But I'll keep an eye on it.