We are currently trialing Octopus and have a step to deploy S3. In that step we set metadata on a single file. The meta data is for Key: Cache-Control, Value: no-cache, no-store, max-age=0.
This is definitely an oversight on our behalf. I have created an issue which you can use to track progress. I believe using an AWS CLI script step may be a possible workaround in the interim albeit less than ideal.
I would like to apologize for any inconvenience this may have caused you and we will try and rectify this as soon as possible.
Sorry to resurrect this -
Has this issue been resolved? I see the Issue has been closed but am encountering similar issues with setting Content-Type on 2019.6.0
It would be nicer/cleaner to have this as all one step