jssimporter / Spruce

Spruce is deprecated. Please see the wiki for alternatives.
GNU General Public License v3.0
148 stars 22 forks source link

Check for usage in Configurations as well... #3

Closed everetteallen closed 9 years ago

everetteallen commented 9 years ago

This is really an enhancement I think. I got feedback from several of my Casper Site admins that they had 10s to 100s of packages that are used only in Casper Configurations and not policies. Our folks would be interested in packages and scripts that are not used in anything (policy, configuration, whatever).

sheagcraig commented 9 years ago

Ah! Cool idea. I'll put that on the todo list for sure.

amandaw33 commented 9 years ago

We have so many packages & scripts in configs, I'd love to have this functionality as well to really be able to utilize Spruce.

kernsb commented 9 years ago

I'll add a "me too" to this one. Ran into this right away.

sheagcraig commented 9 years ago

@everetteallen @amandaw33 @kernsb Check out Spruce 2.0. I don't use the Casper Imaging Configs, so I can't really test, but the code is all there and there's no reason it shouldn't work.

kernsb commented 9 years ago

Awesome! Was just starting to test with that now.

Thanks much for all of your work on this!

Brandon

kernsb commented 9 years ago

Just tested. This is indeed working properly! Scripts and Packages that I was previously having to manually remove from the report because they were being used in Casper Imaging are no longer appearing in the reports!

Brandon

everetteallen commented 9 years ago

Just to confirm this does work as desired. I used my test cloud instance to verify so working with jamfcloud.com hosted JSS instances. Thanks!