Jira (PUP-10607) Add intentional_change, noop_pending_(intentional/corrective) readers to the report processor API

[Enis Inan (Jira)]

Enis Inan created an issue

Puppet / PUP-10607 Add intentional_change, noop_pending_(intentional/corrective) readers to the report processor API Issue Type: New Feature Assignee: Unassigned Created: 2020/08/05 11:32 AM Priority: Normal Reporter: Enis Inan These are already documented event types in https://puppet.com/docs/pe/2019.8/analyze_changes_across_runs.html#event_types so they're available at the event level. The work here involves making these parameters available as a global summary (so at the report processor level). Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Enis Inan (Jira)]

Enis Inan updated an issue

Puppet / PUP-10607 Add intentional_change, noop_pending_(intentional/corrective) readers to the report processor API

Change By: Enis Inan

These are already documented event types in https://puppet.com/docs/pe/2019.8/analyze_changes_across_runs.html#event_types so they're available at the event level. The work here involves making these parameters available as a global summary (so at the report processor level).

Note that {{intentional_change}} is the [corrective_change|https://github.com/puppetlabs/puppet/blob/6.17.0/lib/puppet/transaction/report.rb#L126]-reader analogue for intentional changes. {{noop_pending_(intentional/corrective)}} are more fine-grained readers of the [noop_pending|https://github.com/puppetlabs/puppet/blob/6.17.0/lib/puppet/transaction/report.rb#L81] parameter. For example, {{noop_pending_intentional}} is true if there are any intentional changes that weren't applied because of noop.

Add Comment

[Enis Inan (Jira)]

Enis Inan updated an issue

Puppet / PUP-10607 Add intentional_change, noop_pending_(intentional/corrective) readers to the report processor API Change By: Enis Inan

These are already documented event types in https://puppet.com/docs/pe/2019.8/analyze_changes_across_runs.html#event_types so they're available at the event level. The work here involves making these parameters available as a global summary (so at the report processor level). Note that {{intentional_change}} is the [corrective_change|https://github.com/puppetlabs/puppet/blob/6.17.0/lib/puppet/transaction/report.rb#L126]-reader analogue for intentional changes.

{{noop_pending_(intentional/corrective)}} are more fine-grained readers of the [noop_pending|https://github.com/puppetlabs/puppet/blob/6.17.0/lib/puppet/transaction/report.rb#L81] parameter reader . For example, {{noop_pending_intentional}} is true if there are any intentional changes that weren't applied because of noop.

Add Comment

[Enis Inan (Jira)]

Enis Inan updated an issue

Puppet / PUP-10607 Add intentional_change, noop_pending_(intentional/corrective) readers to the report processor API Change By: Enis Inan

These are already documented event types in https://puppet.com/docs/pe/2019.8/analyze_changes_across_runs.html#event_types so they're available at the event level. The work here involves making these parameters available as a global summary (so at the report processor level). Note that

{{intentional_change}} is the [corrective_change|https://github.com/puppetlabs/puppet/blob/6.17.0/lib/puppet/transaction/report.rb#L126]-reader analogue for intentional changes. {{noop_pending_(intentional/corrective)}} are more fine-grained readers of the [noop_pending|https://github.com/puppetlabs/puppet/blob/6.17.0/lib/puppet/transaction/report.rb#L81] reader. For example, {{noop_pending_intentional}} is true if there are any intentional changes that weren't applied because of noop.

Add Comment