Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-7178

dsc_lite: Modify the output report for dsc_lite resources to prefix type names with dsc_lite_#{resource_name}

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Normal
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: dsc_lite
    • Labels:
      None
    • Template:
    • Acceptance Criteria:
      Hide
      • the last run report contains metrics and resource_type settings for each specific dsc type (based on resource_name) rather than the generic name dsc - manual validation only)
      • PE console accordnigly reports resources as dsc_lite_# {resource_name}

        instead of dsc

      • the existing dsc module can be installed alongside dsc_lite and there are no reporting conflicts (when resource titles are the same - i.e. a dsc resource with a resource_name of file named foo and a dsc_file resource named foo)
      Show
      the last run report contains metrics and resource_type settings for each specific dsc type (based on resource_name ) rather than the generic name dsc - manual validation only) PE console accordnigly reports resources as dsc_lite_# {resource_name} instead of dsc the existing dsc module can be installed alongside dsc_lite and there are no reporting conflicts (when resource titles are the same - i.e. a dsc resource with a resource_name of file named foo and a dsc_file resource named foo )
    • Epic Link:
    • Team:
      Windows
    • Story Points:
      1
    • Sprint:
      Windows 2018-07-18
    • QA Risk Assessment:
      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-8746 patch necessary/should there be any guards in the module code for puppet version?

      UPDATE 7/16/2018:

      Erick Banks 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

            Activity

              People

              Assignee:
              michael.lombardi Michael Lombardi
              Reporter:
              glenn.sarti Glenn Sarti
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support