Summary of the new feature / enhancement
As a user, I want a Microsoft.PowerShell.PSResourceGet/PSResource resource so that a single module or script can be declared without wrapping it in a PSResourceList, and a Microsoft.PowerShell.PSResourceGet/RepositoryList resource so that the full set of registered repositories can be declared in one instance, in the same way PSResourceList does for resources.
Example of what a PSResource instance could look like:
resources:
- name: Pester
type: Microsoft.PowerShell.PSResourceGet/PSResource
properties:
name: Pester
version: '[5.0.0, 6.0.0)'
repositoryName: PSGallery
scope: CurrentUserProposed technical implementation details (optional)
- Add
psresource.dsc.resource.json and repositorylist.dsc.resource.json next to the existing manifests.
- Implement
get, set, test, delete, export and whatIf for both in psresourceget.ps1, reusing GetPSResourceListActions and the Repository class so the behaviour matches the list resources.
Summary of the new feature / enhancement
As a user, I want a
Microsoft.PowerShell.PSResourceGet/PSResourceresource so that a single module or script can be declared without wrapping it in aPSResourceList, and aMicrosoft.PowerShell.PSResourceGet/RepositoryListresource so that the full set of registered repositories can be declared in one instance, in the same wayPSResourceListdoes for resources.Example of what a
PSResourceinstance could look like:Proposed technical implementation details (optional)
psresource.dsc.resource.jsonandrepositorylist.dsc.resource.jsonnext to the existing manifests.get,set,test,delete,exportandwhatIffor both inpsresourceget.ps1, reusingGetPSResourceListActionsand theRepositoryclass so the behaviour matches the list resources.