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
The JamfUploader processors were designed to work without dependencies, meaning they could be used like any other Shared Processor. However, changes in Jamf Pro that are now rolling out to all customers mean that the primary use case of AutoPkg, that is uploading packages, now depends on a step involving uploading to an S3 bucket. This is very complex to achieve without the boto3 python module.
I was wondering whether you would be willing to add it to the supplied AutoPkg-Python? I know you've not traditionally been a fan of adding requirements that are not core to the functionality of AutoPkg+Munki integration, but this one step would allow the simple use of JamfUploader processors to continue without users having to use pip.
I'd be happy to submit a PR.
The text was updated successfully, but these errors were encountered:
I'd love to see this as well, so we don't have to go back to the days of/method that JSSImporter (used).
The only issue I could imagine would be if there was ever an issue where we'd have to "wait" for AutoPkg to be updated for boto3 to be updated. Though, obviously anyone can still update locally using pip.
The JamfUploader processors were designed to work without dependencies, meaning they could be used like any other Shared Processor. However, changes in Jamf Pro that are now rolling out to all customers mean that the primary use case of AutoPkg, that is uploading packages, now depends on a step involving uploading to an S3 bucket. This is very complex to achieve without the
boto3
python module.I was wondering whether you would be willing to add it to the supplied AutoPkg-Python? I know you've not traditionally been a fan of adding requirements that are not core to the functionality of AutoPkg+Munki integration, but this one step would allow the simple use of JamfUploader processors to continue without users having to use
pip
.I'd be happy to submit a PR.
The text was updated successfully, but these errors were encountered: