Thanks for getting in touch! My best guess at the moment is you are using the
Amazon S3 Upload step from the community library which calls
Write-S3Object here. It looks like this step template was built to target a version of the
Write-S3Object cmdlet which accepted a
bool argument for
Recurse, but the version of the cmdlet on your server requires an enum value.
We now have built-in support for uploading things to S3 buckets which is more flexible. I would recommend switching over to use that instead if possible. We kept the community provided step template so people could keep using that if they preferred.
If you are still having trouble after switching over, can you confirm which version of Octopus Server you are using when this happens?
Also can you grab two things and send those through to firstname.lastname@example.org with a link to this post so we can investigate further, then report back on the thread?
- The raw task log for this failing deployment: https://octopus.com/docs/support/get-the-raw-output-from-a-task
- The JSON export of the deployment process (or just that step). You can do this within the Octopus UI itself.
Hope that helps!