Uploaded image for project: 'Puppet Communications Protocol'
  1. Puppet Communications Protocol
  2. PCP-853

Update pxp-agent service to use windows API directly, not nssm

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
    • Acceptance Criteria:
      Hide

      pxp-agent uses the windows API, not nssm, to create/handle the pxp-agent service.

      Show
      pxp-agent uses the windows API, not nssm, to create/handle the pxp-agent service.
    • Team:
      Platform OS
    • QA Risk Assessment:
      Needs Assessment

      Description

      Currently, pxp-agent leverages https://nssm.cc/ to create a windows service. However we need to build nssm as a component of the agent and the project itself hasn't been updated in over a year (not to mention we aren't even on the latest release of nssm).

       

      We should update pxp-agent to work directly with the windows API (rather than nssm) to create/handle the pxp-agent service. This allows us to 'control our own destiny' with the service and remove an older vendored component from the agent.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            sean.mcdonald Sean McDonald
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Zendesk Support