Downloads:

4,427

Downloads of v 1.175.1:

1,018

Last Update:

9/11/2014

Package Maintainer(s):

Software Author(s):

  • PowerShell Team

Tags:

DSC.PowershellCommunity admin dsc desired state configuration powershell

PowerShell Community DSC Modules

1.175.1 | Updated: 9/11/2014

Downloads:

4,427

Downloads of v 1.175.1:

1,018

Maintainer(s):

Software Author(s):

  • PowerShell Team

PowerShell Community DSC Modules 1.175.1

Some Checks Have Failed or Are Not Yet Complete

1 Test Unknown and 1 Failing Test


Validation Testing Unknown


Verification Testing Failed

Details

To install PowerShell Community DSC Modules, run the following command from the command line or from PowerShell:

>

To upgrade PowerShell Community DSC Modules, run the following command from the command line or from PowerShell:

>

To uninstall PowerShell Community DSC Modules, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade dsc.powershellcommunity -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade dsc.powershellcommunity -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure dsc.powershellcommunity installed
  win_chocolatey:
    name: dsc.powershellcommunity
    state: present
    version: 1.175.1
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'dsc.powershellcommunity' do
  action    :install
  version  '1.175.1'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: dsc.powershellcommunity,
    Version: 1.175.1,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller dsc.powershellcommunity
{
   Name     = 'dsc.powershellcommunity'
   Ensure   = 'Present'
   Version  = '1.175.1'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'dsc.powershellcommunity':
  provider => 'chocolatey',
  ensure   => '1.175.1',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install dsc.powershellcommunity version="1.175.1" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was submitted prior to moderation and has not been approved. While it is likely safe for you, there is more risk involved.

Description

Desired State Configuration Modules to augment the initial offering in PowerShell V4


tools\chocolateyInstall.ps1
$mydir = (Split-Path -parent $MyInvocation.MyCommand.Definition)
$toolsDir = ($mydir | Split-Path | Join-Path -ChildPath "tools")

$srcRoot = "$toolsDir\$packageName"

Import-Module PsGet
Install-ChocolateyZipPackage -PackageName $packageName `
                    -url "https://github.com/PowerShellOrg/DSC/archive/e006ad8a0fdb45c40921943f63af32be581a8f5d.zip" `
                    -unzipLocation "$srcRoot" `
                    -specificFolder ""


function Install-PSModuleFolders {
    param([string]$TopLevelFolderPath)

    #Get all top level folders from the "Resources" sub-folder
    $moduleFolders = gci $TopLevelFolderPath  -Directory
    write-host -ForegroundColor cyan ($moduleFolders|out-string)
    foreach($hostModuleFolder in $moduleFolders) {
        try {
            Write-host -ForegroundColor Green ("hostModuleFOlder: {0}" -f ($hostModuleFolder|out-string))
            $module = gci $hostModuleFolder.FullName -Filter "*.psd1"
            if(-not $module) {
                $module = gci $hostModuleFolder.FullName -Filter "*.psm1"
            }
            Write-host -ForegroundColor Green ([io.path]::GetFileNameWithoutExtension($module))
            Write-host -ForegroundColor Green $module.FullName

            #Install modules without importing (some are DSC resource only module, and ought not be treated as regular PowerShell modules)
            Install-Module -modulename ([io.path]::GetFileNameWithoutExtension($module)) -modulepath $module.Parent.FullName -global -force -DoNotImport:$true
        } catch {
            Write-Warning $_
        }
    }
}



$resources = gci $srcRoot -Filter "Resources" -Directory -Recurse | Select-Object -First 1 -Wait
Install-PSModuleFolders -TopLevelFolderPath $resources.FullName

$toolFolders = gci $srcRoot -Filter "Tooling" -Directory -Recurse | Select-Object -First 1 -Wait
Install-PSModuleFolders -TopLevelFolderPath $toolFolders.FullName







In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
PowerShell Community DSC Modules 1.144.1 333 Friday, July 25, 2014 Unknown
PowerShell Community DSC Modules 1.122.1 340 Wednesday, May 21, 2014 Unknown
PowerShell Community DSC Modules 1.120.1 296 Thursday, May 1, 2014 Unknown
PowerShell Community DSC Modules 1.119.1 306 Wednesday, April 9, 2014 Unknown
PowerShell Community DSC Modules 1.114.1 269 Monday, April 7, 2014 Unknown
PowerShell Community DSC Modules 1.95.1 284 Monday, March 24, 2014 Unknown
PowerShell Community DSC Modules 1.76.1 327 Friday, March 7, 2014 Unknown
PowerShell Community DSC Modules 1.75.1 306 Wednesday, March 5, 2014 Unknown
PowerShell Community DSC Modules 1.67.1 288 Thursday, February 20, 2014 Unknown

Initial Release

Discussion for the PowerShell Community DSC Modules Package

Ground Rules:

  • This discussion is only about PowerShell Community DSC Modules and the PowerShell Community DSC Modules package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or PowerShell Community DSC Modules, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus