Rich Siegel

amazing work, from original documentation to merging!!! kudos and @deblasis would be an asset to any org!

I believe (still reviewing) that this dummy package instantiation is causing excessive delays when run over a winrm connection. The answer is always 'windows' as I don't believe you can...

not sure if I put this in the right spot. https://tickets.puppetlabs.com/browse/PUP-11647?filter=-2

you can't set the default provider to chocolatey before puppet runs. If you set Package {provider=chocolatey} that occurs after facter. so I am not sure what this fact accomplishes on...

> custom provider, like the chocolety one, could overwrite the default provider that puppet core sets. Can you substantiate that? If that is the case, I will abandon this effort.

actually I think I am good. I had a misconfigured resource on reverse proxy that was conflicting. A db check might be good, but I don't have a concern with...

does noone manage issues/PRs at hashicorp. how long do things have to lie in wait when the community contributes?

I do this like that: ``` [CmdletBinding()] Param( [Parameter(Mandatory=$True,Position=1)] [string]$titlematch ) start-transcript C:\@inf\winbuild\logs\decline-updates.txt $declineCount = 0 [reflection.assembly]::LoadWithPartialName("Microsoft.UpdateServices.Administration") | Out-Null $wsusServer = [Microsoft.UpdateServices.Administration.AdminProxy]::GetUpdateServer(); $scope = New-Object Microsoft.UpdateServices.Administration.UpdateScope $scope.ApprovedStates = "NotApproved" $updates...

On a side note, have you thought about refactoring this to a module?

I am also missing properties that should be in the MOF as described here https://docs.microsoft.com/en-us/previous-versions/windows/desktop/defender/msft-mpcomputerstatus