You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Tried to find a registered issue that was in some kind resembling mine, but didn’t find any. I have this pretty strange behavior from the chocolateysource resource.
My manifest has this in it:
chocolateysource {'Chocolatey':
ensure => disabled,
}
For some reason on Server 2012 R2 this resource kept on changing the priority from 10 to 0 (I guess 0 is set when a repo is disabled). I remedied this in the ugly way in the past, just adding a priority setting set to 10. Ok, so far so good. Then Server 2016 came along and that ugly fix I had with “priority => 10” resulted in the resource constantly changing the value from 0 to 10, which would be more expected, maybe, then the previous behavior on 2012 R2.
So why is the 2 behaviors different, and which is the right one?
Is this a bug? Expected behavior? Me doing it wrong?
The text was updated successfully, but these errors were encountered:
Could be a bug. However to add more to your confusion, chocolatey/chocolatey does not yet have chocolateysource, chocolateyfeature or chocolateyconfig, those are still only in puppetlabs/chocolatey. That means you will need to file a ticket at https://tickets.puppet.com/browse/MODULES.
It does seem like a bug looking at what you are stating.
Hi,
Tried to find a registered issue that was in some kind resembling mine, but didn’t find any. I have this pretty strange behavior from the chocolateysource resource.
My manifest has this in it:
chocolateysource {'Chocolatey':
ensure => disabled,
}
For some reason on Server 2012 R2 this resource kept on changing the priority from 10 to 0 (I guess 0 is set when a repo is disabled). I remedied this in the ugly way in the past, just adding a priority setting set to 10. Ok, so far so good. Then Server 2016 came along and that ugly fix I had with “priority => 10” resulted in the resource constantly changing the value from 0 to 10, which would be more expected, maybe, then the previous behavior on 2012 R2.
So why is the 2 behaviors different, and which is the right one?
Is this a bug? Expected behavior? Me doing it wrong?
The text was updated successfully, but these errors were encountered: