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
{{ message }}
This repository has been archived by the owner on Feb 19, 2019. It is now read-only.
Rather than have the separate write-chocolateysuccess and write-chocolateyfailure scripts as well as some other functions (such as Chocolatey-Update and Chocolatey-Nuget to name a few) that all provide their own messaging and logging, it would be great to pipe all the info out of those scripts to a centralized logging function. This may make it easier to integrate into Enterprise systems.
For our enterprise implementation, I am creating a Sinatra web service to handle reporting of any Chocolatey activity that changes a system. I am working on funneling all info I need to one function so I may be able to contribute to this project if that is something you might be interested in.
The text was updated successfully, but these errors were encountered:
Rather than have the separate write-chocolateysuccess and write-chocolateyfailure scripts as well as some other functions (such as Chocolatey-Update and Chocolatey-Nuget to name a few) that all provide their own messaging and logging, it would be great to pipe all the info out of those scripts to a centralized logging function. This may make it easier to integrate into Enterprise systems.
For our enterprise implementation, I am creating a Sinatra web service to handle reporting of any Chocolatey activity that changes a system. I am working on funneling all info I need to one function so I may be able to contribute to this project if that is something you might be interested in.
The text was updated successfully, but these errors were encountered: