Details
-
Task
-
Status: Resolved
-
Normal
-
Resolution: Done
-
None
-
None
-
None
-
-
Windows
-
1
-
Windows 2018-07-18
-
Needs Assessment
Description
During MODULES-5970 it was found that altering catalog compilation and catalog application shouldn't (or couldn't) be done. However there was an opportunity/seam that could be exploited in the report generation to help users in the PE Console
Determine if, for the sake of reporting, the generic dsc resource can masquerade under another name. This is important for type filtering in the console.
There is a resource_type value in the Resource::Status class that looks at resource.type.to_s.capitalize that should be settable from the given dsc_resource_name attribute of the dsc resource.
Technical concerns:
- is the type a singleton or not?
- can individual resources vary their types/are there performance implications?
- is the
PUP-8746patch necessary/should there be any guards in the module code for puppet version?
UPDATE 7/16/2018:
erick and I were quickly able to verify that the solution is feasible after spinning up a 2018.1.2 master and modifying reporting. Given how little work was involved, this was changed from a SPIKE to an actual implementation ticket.
Attachments
Issue Links
- relates to
-
MODULES-7485 dsc_lite : 'isrequired' validation does not work
-
- Resolved
-
-
MODULES-5970 DSC_Lite : (SPIKE) Determine if generic `dsc` resource can report itself under a different resource name
-
- Resolved
-
-
PUP-8746 Improve time_metrics in report generation to use existing statuses
-
- Closed
-