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
We probably need at a minimum node['chocolatey'] with the following data:
choco version
choco edition (OSS vs. non-free)
choco config options
We also need to collect package information. We will want to explore if we can mix this data into the existing package data in a way that would make sense or if we just need to expose it here. For a lot of use cases people want to just know what's installed on a system so it would be useful to present that in a single location if possible, but that may require adding something like "provider" to each package entry to mark if it's a system package or a chocolatey package or whatever else comes out.
The text was updated successfully, but these errors were encountered:
i could definitely buy that its windows so that we don't try to dump all the different sources of packages into the node["packages"] hash and make a mess there that is useful for nobody.
We probably need at a minimum
node['chocolatey']
with the following data:We also need to collect package information. We will want to explore if we can mix this data into the existing package data in a way that would make sense or if we just need to expose it here. For a lot of use cases people want to just know what's installed on a system so it would be useful to present that in a single location if possible, but that may require adding something like "provider" to each package entry to mark if it's a system package or a chocolatey package or whatever else comes out.
The text was updated successfully, but these errors were encountered: