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
Describe the solution you'd like
This is a bit of an opinionated ask, but thought I would put it out there.
At present, when a DMG or an app that utilizes a Sparkle feed is dragged into Recipe Robot, when a .pkg recipe is selected to be created all that's included in the .pkg recipe is AppPkgCreator. The only output from this processor is version, but there is frequently other info - like LSMinimumSystemVersion - which would be useful for those admins that utilize non-munki recipes which don't automatically look at or collect this information because they require software deployment through a package. As a result, I would like to see PlistReader be added to acquire any and all applicable software keys, including:
CFBundleIdentifier
CFBundleShortVersionString
CFBundleVersion
LSMinimumSystemVersion
This way for example, if I as a munki admin don't create a .jss recipe with Recipe Robot that someone who comes along and uses my Recipe Robot .pkg recipe as a parent recipe that they can utilize this info. without having to create a separate PR to get this added to my .pkg recipe.
Describe alternatives you've considered
Manually adding these after the fact.
Additional context
Ultimately this isn't something I desperately need by any means. More that for those that use Recipe Robot to build all or the majority of their recipes that it would be best to ensure anyone who creates parent recipes from this that they are to take advantage of these keys & values that we know are important.
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
This is a bit of an opinionated ask, but thought I would put it out there.
At present, when a DMG or an app that utilizes a Sparkle feed is dragged into Recipe Robot, when a .pkg recipe is selected to be created all that's included in the .pkg recipe is
AppPkgCreator
. The only output from this processor isversion
, but there is frequently other info - likeLSMinimumSystemVersion
- which would be useful for those admins that utilize non-munki recipes which don't automatically look at or collect this information because they require software deployment through a package. As a result, I would like to seePlistReader
be added to acquire any and all applicable software keys, including:CFBundleIdentifier
CFBundleShortVersionString
CFBundleVersion
LSMinimumSystemVersion
This way for example, if I as a munki admin don't create a .jss recipe with Recipe Robot that someone who comes along and uses my Recipe Robot .pkg recipe as a parent recipe that they can utilize this info. without having to create a separate PR to get this added to my .pkg recipe.
Describe alternatives you've considered
Manually adding these after the fact.
Additional context
Ultimately this isn't something I desperately need by any means. More that for those that use Recipe Robot to build all or the majority of their recipes that it would be best to ensure anyone who creates parent recipes from this that they are to take advantage of these keys & values that we know are important.
The text was updated successfully, but these errors were encountered: