search

qameta / testops-deploy-helm-chart

Helm Chart for Allure TestOps version 5 deployment in Kubernetes
https://docs.qameta.io/allure-testops/install/kubernetes/
0 stars 0 forks source link

add parameter and its processing for using multiple prefixes for AWS S3 #32

Open cheshi-mantu opened 2 weeks ago

cheshi-mantu commented 2 weeks ago

Context

see the content of PR https://github.com/qameta/allure-server/pull/8048 multiple prefixes on the root level of the bucket allows multiply the allowed RPS per the number of prefixes

Requirements

  1. add new parameter to values.yaml under .Values.storage.s3
  2. Name: awsS3SingleTag
  3. Options: true|false, default = true
  4. Translation into the settings: ALLURE_BLOB_STORAGE_USE_V2_PREFIX <== Values.storage.s3.awsS3SingleTag
  5. Comments to values.yaml: awsS3SingleTag must be used with AWS S3 only (set to false if you are using AWS S3 buckets), the parameter defines whether single or multiple prefixes must be used for the projects in Allure TestOps. In case of true, single prefix and max 3500 RPS will be used, in case of false the final RPS will be 3500rps for each project in Allure TestOps for basic S3 operations.
cheshi-mantu commented 1 week ago

will be done by default on BE side