Allow custom object key for artifacts instead of md5 hash

Describe your idea/feature/enhancement

I don’t know if it’s a bug or not, but the s3 object key of the generated artifacts (using sam package) is the md5 hash of the zip file. On the documentation, I see that the name of the uploaded zip file is the same of the source folder, but I can’t get it work in this way.

I need this, because I want to reference the uploaded object using a data source in Terraform (now I’m parsing the json output of sam package). Furthermore, since the 2 keys are different (different hashes), sam package creates a new object instead of creating a new version of the older artifact.

[acerbisgianluca]

Actually I use SAM only for building and uploading artificats and Terraform to attach them to a function, so I don’t think sam delete would work in my case since I’ve no stack.

I understand, but having such option will bypass de-duplication of the uploads of the artifacts, and that will cost some time during package/deploy operation. Will that be ok for your use case?

What about storing the name (or something else which doesn’t change in each deploy) of the object/package in build.toml? When sam package is run, it would get the latest version of the object with key prefix/name (I think that currently name is the hash of the builded package) and would compare its md5 hash with the one stored in build.toml. If they are equals, then skip the upload, otherwise do it.

[acerbisgianluca]

Hey @rpf3 , sorry for the late reply. Unfortunately I didn’t come up with any solutions. I only created a script in my package.json to delete all the artifacts with a given prefix using AWS cli and I manually run it.