Bug #9660
closed
Technique errors only show up in webapp log
Description
Hi,
When developing techniques, and you have an issue, it would help if it would be displayed somewhere in the webapp, as currently the only place you can retrieve it is the webapp log, like for example:
[2016-11-10 13:26:36] ERROR com.normation.cfclerk.services.impl.GitTechniqueReader - Ignoring technique '/Custom/timeSettings/1.0/metadata.xml' because the descriptor file is malformed. \ Error message was: Unexpected issue with the descriptor file /Custom/timeSettings/1.0/metadata.xml at line 35, column 7: \ The element type "SECTIONS" must be terminated by the matching end-tag "</SECTIONS>".
Updated by Alexis Mousset over 7 years ago
- Has duplicate User story #3339: Display "broken" technique in Techniques screens added
Updated by Benoît PECCATTE about 7 years ago
- Found in version(s) old deleted (
3.1.13)
Updated by Benoît PECCATTE about 7 years ago
- Category set to Web - UI & UX
- Target version set to Ideas (not version specific)
Updated by Benoît PECCATTE about 7 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Priority set to 16
Updated by François ARMAND about 2 years ago
- Status changed from New to Rejected
- Priority changed from 27 to 0
Now, technique are mostly "developped" with the technique editor, or in a near future with rudder lang. In both cases, errors are reported where the user is working (ie in the technique editor, or in rudderc output).
For that one, we don't have an obvious place to report the error to user appart in the log (in UI, in a place like an "admin message console" would make sense, but we don't have that).
So I'm closing that one since it's unlikely that we will find a better way to report these errors, and that kind of technique dev should be less and less common.
If you don't agree with the closing, please let us know, or reopen it.