Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-4866

Plug-in Sync Should Use Long File Name (LFN) Paths on Windows

    Details

    • Type: Improvement
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: PMT, Windows
    • Labels:
    • Template:
    • Team:
      Coremunity
    • Story Points:
      5

      Description

      Splitting PUP-4866 for PMT and Plug-in Sync to have a ticket for each effort.

      This is the Plug-in Sync effort

      It was discovered in PUP-4854 that long file name paths will break PMT and potentially plugin-sync. The PMT and Puppet core libraries should always use LFN (Long File Name aka "\\?\") paths for module installation to avoid long file name issues.

      In PUP-4854 we reduced the amount of characters that PMT uses so that it allows for longer module paths to be installed. It helps with longer paths in modules, but it doesn't address the issue completely. We should instead look to use "\\?\" prepended to the path to allow for up to 32,000 characters in paths instead of the current MAX_PATH limit of 260 characters. See MSDN - Naming Files, Paths, and Namespaces.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  ethan Ethan Brown
                  Reporter:
                  ryan.gard Ryan Gard
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:

                    Zendesk Support