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

DSC - Upstream DSC Resource Repo Git Submodules out of date

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • None
    • None
    • dsc
    • Hide
      • A YAML manifest of DSC xResource versions should be recorded in the repository to track precisely what we're shipping
      • This manifest should be created automatically if none exists. The latest semantic version of a PSGallery style tag should be found in each submodule of the parent PowerShell/DSCResources repository
      • If new submodules are added to the parent DSCResources repository, they should automatically be added to the manifest
      • If submodules are removed from the parent DSCResources repository, they should automatically be removed from the manifest
      • The manifest can be edited by humans to pick an older version of a tagged DSC resource for compatibility or other reasons
      • The build process should only acquire versions from the upstream DSC resources as specified in the manifest, except when the submodule no longer exists or is new. This ensures users should always get the exact versions that we've shipped when they rebuild DSC resources.
      • The rake task should be amended so that a --latest (or similar) switch can be provided to force an update to the latest semantically versioned resources within the submodules
      Show
      A YAML manifest of DSC xResource versions should be recorded in the repository to track precisely what we're shipping This manifest should be created automatically if none exists. The latest semantic version of a PSGallery style tag should be found in each submodule of the parent PowerShell/DSCResources repository If new submodules are added to the parent DSCResources repository, they should automatically be added to the manifest If submodules are removed from the parent DSCResources repository, they should automatically be removed from the manifest The manifest can be edited by humans to pick an older version of a tagged DSC resource for compatibility or other reasons The build process should only acquire versions from the upstream DSC resources as specified in the manifest, except when the submodule no longer exists or is new. This ensures users should always get the exact versions that we've shipped when they rebuild DSC resources. The rake task should be amended so that a --latest (or similar) switch can be provided to force an update to the latest semantically versioned resources within the submodules
    • 3
    • Windows 2016-06-15, Windows 2016-07-27

    Description

      The Puppet DSC module includes (vendors) several existing DSC Resources from the https://github.com/PowerShell/DscResources. This repo is really just a placeholder for a bunch of git submodules. We have relied on it to be accurate and timely updated with new versions of the submodules when Microsoft has released them. Unfortunately it seems they have started to lag in updating the submodules. This ticket is to identify a solution and implement it.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              james.pogran James Pogran
              Glenn Sarti Glenn Sarti
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support