[1.0.2b2] Cannot upload packages to CDP (S3)

Tried out the latest 1.0.1 beta but I’m still running into constant errors. I’ve included some output from autopkg runs which I’m hoping will help track the issue down.

Before running this I did the following: - Deleted the Policy from Jamf - Removed the latest Atom pkg from S3 - Removed the latest Atom pkg from my File Share Distribution Point

The following is a breakdown of what occurred after each run

Run 1: - Atom is downloaded and packaged - Atom pkg record is created in the Jamf server

Run 2: - Atom policy is created on the Jamf Server - Atom pkg is copied to the Local file share - Atom pkg is uploaded to S3 but the file is broken (only 70MB vs 132MB)

Run 3: (Before running I delete the pkg record from Jamf which also removes the broken file from S3 and from the Policy) - Package record is created in Jamf - No File is uploaded to S3 - No Package is attached to the Atom Policy

JSSImporter error log.txt

[mosen]

I believe that somewhere between Jamf Pro 10.5.0 and 10.7.1 the implementation of /dbfileupload was changed. This is the URL that JSSImporter has always used to upload packages for CDP, JCDS and JDS.

Seeing as this option seems deprecated/end of life and we don’t have an official API, I would like to offer direct upload options for AWS S3 CDP and JCDS (which already exists).

The old distribution point “CDP” will remain for people running older versions of JAMF Pro.

[grahampugh]

Closing this as it relates to the old version that used curl. If anyone is still seeing the issue, comment here and I’ll reopen.