Bug #5756
When a resource is being audited for the first time it should produce an event
| Status: | Accepted | Start date: | 01/03/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | auditing/compliance | |||
| Target version: | - | |||
| Affected Puppet version: | Branch: | |||
| Keywords: | ||||
Description
Currently the first audit run for a resource doesn’t create an event in the report that is produced, but it does log that a new audited value was recorded. Perhaps this is desired behavior. Perhaps not. It probably depends on how people consuming report events are likely to act on that information, and I don’t think we have the user stories clear enough for how reports are used to make that decision.
History
#1
Updated by James Turnbull over 2 years ago
- Category set to auditing/compliance
- Status changed from Unreviewed to Needs Decision
- Assignee set to Nigel Kersten
#2
Updated by Nigel Kersten over 2 years ago
- Status changed from Needs Decision to Accepted
- Assignee deleted (
Nigel Kersten) - Target version set to 2.7.x
#3
Updated by Andrew Parker 6 months ago
- Target version deleted (
2.7.x)
#4
Updated by Andrew Parker 6 months ago
As the 2.7.x line is winding down, I am removing the target at 2.7.x from tickets in the system. The 2.7 line should only receive fixes for major problems (crashes, for instance) or security problems.