We're planning to unprototype Drydock in the cluster soon (see parent task T10246). Before doing this, there are some technical and usability issues in Harbormaster and Drydock that I want to try to clean up.
Revisions and Commits
- Mentioned In
- Blog Post: Development Notes (2016 Week 9)
T5822: Implement garbage collection / automatic archiving for Harbormaster logs
- Mentioned Here
- T7449: Support ANSI escaped color sequences in Paste
T8656: Parse ANSI-style color strings in build output
T10246: Deploy Drydock in the Phacility cluster
Is support of ansi color possible in this harbormaster iteration ? I mean not only parse the ansi code but also generate a markup based on the color.
As far as I remenber it wasn't the case.
Sometimes some information highlight are really usefull : in my ansible deploy (as a use case), they differentiate the log level.
But I understand if harbormaster console isn't the higher priority.
@epriestley : sorry, I should have searched more thoughtfully.
Is it something community can do ?
If so, where shall I start ?
So far, if my contribution can interest you, i would :
- first implement a ANSI parser that strip out ansi code (like [33m ) replacing it by U+FFF9 or U+FFFB depending if it is an ansi open code or an ansi close : this would be a PhutilMarkupEngine, right ?
- generate a syntax highlighter ( iw ould learn how to do it based on PhutilRainbowSyntaxHighlighter)
If you agree on this, I would open a new feature request task, and start diffing.