Request: Document the IAM profile needed for Artifacts object storage
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
The Job Artifacts documentation does not describe which permissions Gitlab will need to store / retrieve artifacts and logs. This seems like a missing part :).
I'm currently implementing this, and will try with a plain Get/Put/List setup ... I'll report back with my findings.
The documentation also states:
Currently this has to be executed manually and it will allow you to migrate the existing artifacts to the object storage, but all new artifacts will still be stored on the local disk. In the future you will be given an option to define a default storage artifacts for all new files.
While, further up, it says:
direct_upload Set to true to enable direct upload of Artifacts without the need of local shared storage. Option may be removed once we decide to support only single storage for all files.; default: false
background_upload Set to false to disable automatic upload. Option may be removed once upload is direct to S3; default: true
... which really contradicts itself, right?