PSDscResources | new home of the in-box resources | Frontend Framework library
kandi X-RAY | PSDscResources Summary
kandi X-RAY | PSDscResources Summary
PSDscResources is the new home of the in-box resources from PSDesiredStateConfiguration. The resources in this module are maintained and supported by Microsoft. These resources are a combination of those in the in-box PSDesiredStateConfiguration module as well as community contributions from our experimental xPSDesiredStateConfiguration module on GitHub. These resources have also recently been updated to meet the DSC Resource Kit High Quality Resource Module (HQRM) guidelines. In-box resources not currently included in this module should not be affected and can still load from the in-box PSDesiredStateConfiguration module. Because PSDscResources overwrites in-box resources, it is only available for WMF 5.1. Many of the resource updates provided here are also included in the xPSDesiredStateConfiguration module which is still compatible with WMF 4 and WMF 5 (though this module is not supported and may be removed in the future).
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of PSDscResources
PSDscResources Key Features
PSDscResources Examples and Code Snippets
Community Discussions
Trending Discussions on PSDscResources
QUESTION
I am executing Powershell DSC script from Powershell. Below is the code snippet
...ANSWER
Answered 2020-Sep-08 at 08:31You can add a named Parameter $driveformat
in your script. See below example:
QUESTION
I'm having an issue where PowerShell DSC resources are failing to import during a Packer job being run through Azure Pipelines.
Packer indicates an error saying:
...ANSWER
Answered 2020-Mar-13 at 18:50The problem you're seeing is that DSC configs are parsed before any code in the file is run, even before they are loaded into memory. If the modules aren't there before the config script is run then it'll fail. You'll be better off installing those modules before you run the config, probably in a separate Packer step.
QUESTION
I'm observing the following behavior when trying to retrieve Automation modules from automation account using Get-AzureRmAutomationModule cmdlet.
When using the cmdlet with only 2 parameters (ResourceGroupName and AutomationAccountName), the modules list shows Version as null for the "global" modules. However, when running the same cmdlet by passing 3 parameters (ResourceGroupName, AutomationAccountName, and Module name), we get the version for the global modules.
Is this as designed and if so, why is it in this way? Currently, the portal also shows version as null for the global modules when in fact they have a version already. Some sample modules where this behavior is seen are listed below.
...ANSWER
Answered 2018-Aug-03 at 09:42Here are some personal opinions for you to refer, I think it may be a bug of the API.
First, I check it in the portal and test the command, the result is like you mentioned, but the command is essentially an API. So I check my automation account in the azure resource explorer(choose the AuditPolicyDsc
module for sample).
Check all the modules:
Check only the AuditPolicyDsc
module:
You could find the AuditPolicyDsc
module, not only the version
, but also the sizeInBytes
and activityCount
are different.
Note: Also, I think it may not be related to global, you could find a module named Microsoft.PowerShell.Core
, it is global but the version is not null.
They use two different API, I think it may caused by them, otherwise it may be unreasonable.
QUESTION
Here's my example:
...ANSWER
Answered 2017-Oct-27 at 17:25You won't find this in the documentation because you (basically) can't do that.
I say basically, because you can do it, in a sense, with DSC Partial Configurations.
These require a different workflow and a different Local Configuration Manager (LCM) setup though. They do not work the way you are envisioning where you create multiple configurations and then apply them one after the other.
This is by design; what you're trying to do isn't really what DSC is for. The idea is that you are supposed to be supplying the (desired) state of the node you're configuring. Applying multiple configurations could easily cause conflicting settings to be applied.
Even with partials, the LCM is generating a single configuration (resolving your partials) and then applying that all at once.
What to do instead:DSC is light on tooling. It doesn't really have much to say about how you ultimately generate your configs or handle common data, roles, etc. So you already have to roll your own for the most part.
Applying multiple separate configurations is probably something you should be taking care of in your own workflow, leading up to ultimately compiling your (single) MOF per node.
What are Partials For?There are 2 use cases I can think of where it would be appropriate to use Partials.
First (and this is primarily the role for them Microsoft had in mind) is for larger and more segregated organizations, where different teams have sole responsibility and ownership for their knowledge domain, and you want those teams to be able to write and control their own configurations.
So for example, the OS team might write the configuration for various basic OS config items (setting time zone/NTP, license settings), and maybe they set the LCM setup to pull from the rest.
The DBA team writes a configuration for installing and configuring SQL server.
The security team writes a configuration for setting password policies, firewall rules and enforcement, etc.
These teams have their own procedures and rules and autonomy. They may have their own pull server where they publish these.
The second use case, which is often related to the first, is when you have multiple pull servers, or you want to combine push and pull. I believe that's only possible with partials.
FutureDo note that Windows PowerShell is unlikely to be updated anymore. PowerShell Core (which is based on .Net Core and runs on Windows, Linux, and MacOS) is where the majority of PowerShell development is going at this time.
With that, DSC will be changing too and getting a completely new edition going forward that works better cross-platform.
Just something to keep in mind if you're going down the path of writing a lot of tooling and workflow code to support DSC.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install PSDscResources
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page