The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
Telly requires a single console log output mechanism, but will have two after PMT merges up.
|Assignee:||Chris Price||% Done:|
|Affected Puppet version:||Branch:||https://github.com/puppetlabs/puppet/pull/692|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.
While the PMT work was underway, a new console output mechanism was needed. This was added in 2.7.x, the stable series, as an addition used only in the PMT code itself.
Now that has merged to the main tree, and we are starting to look at Telly, we need to have this fixed. We can’t ship Telly with two log output mechanisms.
#2 Updated by Anonymous almost 3 years ago
Having received feedback that this isn’t at all clear about what happens next:
The immediate step is that I need you, Pieter, to make the following decisions:
- which console log mechanism is going to exist in Telly?
- what does that change for our users?
- what documentation effect does that have?
- what other changes need to be made in Puppet to reflect this?
Specifically, if the new log mechanism is going to continue to exist I need to know the full set of UX requirements around it: where it works, how it works, how compatibility is maintained or broken, what documentation changes are required, and any other UX drivers that I am not aware of yet.
#7 Updated by Anonymous over 2 years ago
The plan to correct this is that we will update the new console code to include the context – unless that is “Puppet” only. That still gives the right “what” most of the time, but reduces visual noise.
Comparing to the previous version of the console output mechanism will show how the context was included, but basically,