Actions
Bug #18102
closed
Bug #18100: Techniques with conditions on tasks with very long parameters report "missing" parts on the dashboard
create a specific bundle specific for NA reports
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
to create NA reports, we define a class noop based on the technique name, technique parameters, and use it on reports, along with some old_class_prefix
But it may fail if parameter is too long (longer than 1000 characters) as content is added afterward
also, it can cause leaks of reports from one method to another
we could simply call a wrapper that would call the na report, and skipping the class definition part (as the class is non standart)
Updated by Nicolas CHARLES over 4 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES over 4 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/ncf/pull/1236
Updated by Nicolas CHARLES over 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset ncf:commit:14b4ba5414f9553adfea9055c33009a4919320f7.
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.0.9 to 6.0.8
Updated by Vincent MEMBRÉ about 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.8 and 6.1.4 which were released today.
Updated by Benoît PECCATTE about 4 years ago
- Subject changed from create a bundle specific pour NA reports to create a specific bundle specific for NA reports
Actions