zuul-jobs/roles/upload-logs-s3
James E. Blair 622baa65bf Add no_log to all log upload tasks
Some log upload tasks were missing no_log instructions and might
write out credentials to the job-output.json file.  Update these
tasks to include no_log.

Change-Id: I1f18cec117d9205945644ce19d5584f5d676e8d8
2022-11-16 09:11:12 -08:00
..
defaults Add configuration to make logs public 2020-12-21 18:12:25 +01:00
meta Merge upload logs modules into common role 2020-09-25 13:21:12 +02:00
tasks Add no_log to all log upload tasks 2022-11-16 09:11:12 -08:00
README.rst Revert "Update upload-logs roles to support endpoint override" 2021-02-19 09:08:24 -08:00

Upload logs to S3

Before using this role, create at least one bucket and set up appropriate access controls or lifecycle events. This role will not automatically create buckets.

This role requires the boto3 Python package to be installed in the Ansible environment on the Zuul executor.

Role Variables

This role will not create buckets which do not already exist. If partitioning is not enabled, this is the name of the bucket which will be used. If partitioning is enabled, then this will be used as the prefix for the bucket name which will be separated from the partition name by an underscore. For example, "logs_42" would be the bucket name for partition 42.

Note that you will want to set this to a value that uniquely identifies your Zuul installation.

AWS access key to use.

AWS secret key for the AWS access key.

The endpoint to use when uploading logs to an s3 compatible service. By default this will be automatically constructed by boto but should be set when working with non-aws hosted s3 service.