Modules

Topics

Resources

PuppetEcosystemPuppet CommunityUpdates

sharepointdsc

supported
pdk
This DSC module is used to deploy and configure SharePoint Server 2013, 2016 and 2019, and covers a wide range of areas including web apps, s...
Project URLRSS FeedReport issues

Autogenerated DSC Modules

dsc

3,163 downloads

805 latest version

4.5 quality score

Version information

  • 4.4.0-0-1 (latest)
  • 4.4.0-0-0
  • 4.3.0-0-1
  • 4.3.0-0-0
  • 4.2.0-0-2
  • 4.2.0-0-1
  • 4.2.0-0-0
  • 4.1.0-0-1
  • 4.1.0-0-0
  • 4.0.0-0-1
  • 4.0.0-0-0
  • 3.8.0-0-1
  • 3.8.0-0-0
  • 3.7.0-0-1
  • 3.7.0-0-0
  • 3.6.0-0-1
  • 3.6.0-0-0
  • 3.5.0-0-1
  • 3.5.0-0-0
  • 3.4.0-0-1
  • 3.4.0-0-0
  • 3.3.0-0-1
  • 3.3.0-0-0
  • 3.2.0-0-1
  • 3.2.0-0-0
  • 3.1.0-0-1
  • 3.1.0-0-0
  • 3.0.0-0-1
  • 3.0.0-0-0
  • 2.6.0-0-1
  • 2.6.0-0-0
  • 2.5.0-0-1
  • 2.5.0-0-0
  • 2.4.0-0-1
  • 2.4.0-0-0
  • 2.3.0-0-1
  • 2.3.0-0-0
  • 2.2.0-0-1
  • 2.2.0-0-0
  • 2.1.0-0-1
  • 2.1.0-0-0
  • 2.0.0-0-1
  • 2.0.0-0-0
  • 1.9.0-0-1
  • 1.9.0-0-0
  • 1.8.0-0-1
  • 1.8.0-0-0
  • 1.7.0-0-1
  • 1.7.0-0-0
  • 1.6.0-0-1
  • 1.6.0-0-0
  • 1.5.0-0-1
  • 1.5.0-0-0
  • 1.4.0-0-1
  • 1.4.0-0-0
  • 1.3.0-0-1
  • 1.3.0-0-0
  • 1.2.0-0-1
  • 1.2.0-0-0
  • 1.1.0-0-1
  • 1.1.0-0-0
  • 1.0.0-0-1
  • 1.0.0-0-0
released Jan 28th 2021
This version is compatible with:
  • Puppet Enterprise 2021.1.x, 2021.0.x, 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x
  • Puppet >= 6.0.0 < 8.0.0
  • windows

Start using this module

Documentation

dsc/sharepointdsc — version 4.4.0-0-1 Jan 28th 2021

Table of Contents

  1. Description
  2. Requirements
  3. Usage
  4. Troubleshooting

Description

This is an auto-generated module, using the Puppet DSC Builder to vendor and expose the PowerShell module's DSC resources as Puppet resources. The functionality of this module comes entirely from the vendored PowerShell resources, which are pinned at v4.4.0. The PowerShell module describes itself like this:

This DSC module is used to deploy and configure SharePoint Server 2013, 2016 and 2019, and covers a wide range of areas including web apps, service apps and farm configuration.

For information on troubleshooting to determine whether any encountered problems are with the Puppet wrapper or the DSC resource, see the troubleshooting section below.

Requirements

This module, like all auto-generated Puppetized DSC modules, relies on two important technologies in the Puppet stack: the Puppet Resource API and the puppetlabs/pwshlib Puppet module.

The Resource API provides a simplified option for writing types and providers and is responsible for how this module is structured. The Resource API ships inside of Puppet starting with version 6. While it is technically possible to add the Resource API functionality to Puppet 5.5.x, the DSC functionality has not been tested in this setup. For more information on the Resource API, review the documentation.

The module also depends on the pwshlib module. This Puppet module includes two important things: the ruby-pwsh library for running PowerShell code from ruby and the base provider for DSC resources, which this module leverages.

All of the actual work being done to call the DSC resources vendored with this module is in this file from the pwshlib module. This is important for troubleshooting and bug reporting, but doesn't impact your use of the module except that the end result will be that nothing works, as the dependency is not installed alongside this module!

Usage

You can specify any of the DSC resources from this module like a normal Puppet resource in your manifests. The examples below use DSC resources from from the PowerShellGet repository, regardless of what module you're looking at here; the syntax, not the specifics, is what's important.

For reference documentation about the DSC resources exposed in this module, see the Reference Forge tab, or the REFERENCE.md file.

# Include a meaningful title for your resource declaration
dsc_psrepository { 'Add team module repo':
    dsc_name               => 'foo',
    dsc_ensure             => present,
    # This location is nonsense, can be any valid folder on your
    # machine or in a share, any location the SourceLocation param
    # for the DSC resource will accept.
    dsc_sourcelocation     => 'C:\Program Files',
    # You must always pass an enum fully lower-cased;
    # Puppet is case sensitive even when PowerShell isn't
    dsc_installationpolicy => untrusted,
}

dsc_psrepository { 'Trust public gallery':
    dsc_name               => 'PSGallery',
    dsc_ensure             => present,
    dsc_installationpolicy => trusted,
}

dsc_psmodule { 'Make Ruby manageable via uru':
  dsc_name   => 'RubyInstaller',
  dsc_ensure => present,
}

For more information about using a built module, check out our narrative documentation.

Properties

Note that the only properties specified in a resource declaration which are passed to Invoke-Dsc are all prepended with dsc. If a property does _not start with dsc_ it is used to control how Puppet interacts with DSC/other Puppet resources - for example, specifying a unique name for the resource for Puppet to distinguish between declarations or Puppet metaparameters (notifies, before, etc).

Troubleshooting

In general, there are three broad categories of problems:

  1. Problems with the way the underlying DSC resource works.
  2. Problems with the type definition, where you can't specify a valid set of properties for the DSC resource
  3. Problems with calling the underlying DSC resource - the parameters aren't being passed correctly or the resource can't be found

Unfortunately, problems with the way the underlying DSC resource works are something we can't help directly with. You'll need to file an issue with the upstream maintainers for the PowerShell module.

Problems with the type definition are when a value that should be valid according to the DSC resource's documentation and code is not accepted by the Puppet wrapper. If and when you run across one of these, please file an issue with the Puppet DSC Builder; this is where the conversion happens and once we know of a problem we can fix it and regenerate the Puppet modules. To help us identify the issue, please specify the DSC module, version, resource, property and values that are giving you issues. Once a fix is available we will regenerate and release updated versions of this Puppet wrapper.

Problems with calling the underlying DSC resource become apparent by comparing <value passed in in puppet> with <value received by DSC>. In this case, please file an issue with the puppetlabs/pwshlib module, which is where the DSC base provider actually lives. We'll investigate and prioritize a fix and update the puppetlabs/pwshlib module. Updating to the pwshlib version with the fix will immediately take advantage of the improved functionality without waiting for this module to be reconverted and published.

For specific information on troubleshooting a generated module, check the troubleshooting guide for the puppet.dsc module.

Known Limitations

Currently, because of the way Puppet caches files on agents, use of the legacy puppetlabs-dsc module is not compatible with this or any auto-generated DSC module. Inclusion of both will lead to pluginsync conflicts.