Allow job traces to be placed in specific key when using object storage

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

Currently it appears that it is not possible to specify a dedicated key/prefix for job traces when using remote object storage. We would like the ability to be able to separate out job traces from other artifacts so that we may apply different appropriate S3 lifecycle policies.

Previously, when using local storage I believe it was possible to set a specific location for job traces. We would like this functionality also for remote object storage