-
Notifications
You must be signed in to change notification settings - Fork 34
Need resource definition caching #249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Here is the current list of properties $resourceOutput = [resourceOutput]@{
type = $Type
version = $r.version.ToString()
path = $r.Path
directory = $r.ParentPath
implementedAs = $r.ImplementationDetail
author = $r.CompanyName
properties = $r.Properties.Name
requires = $requiresString
} I would like to propose that we do not need "Directory" nor "Author". Thoughts? I would also propose that we need a Finally, I would suggest that dsc resource cache information could be stored in the following locations. Windows: |
@mgreenegit couple of thoughts:
|
This is implemented for PS-class-based DSC resources that go through PS adapter; |
Resolved for PowerShell group resource |
Prerequisites
Steps to reproduce
Currently each
dsc.exe
operation as a first step performs resource discovery available on the system.This is relatively slow process especially for resource providers like
DSC/PowerShellGroup
.On the other hand, resource definitions do not change often, so their caching will help a lot with speed of
dsc.exe
operations.Expected behavior
NA
Actual behavior
NA
Error details
No response
Environment data
Version
v1
Visuals
No response
The text was updated successfully, but these errors were encountered: