diff --git a/argocd/apps/openproject/values-openproject.yaml b/argocd/apps/openproject/values-openproject.yaml index 371216e..ca5a0ec 100644 --- a/argocd/apps/openproject/values-openproject.yaml +++ b/argocd/apps/openproject/values-openproject.yaml @@ -78,48 +78,6 @@ spec: password_reset: "false" name: "OpenProject Admin" mail: "inno-netz@innovation-hub-niedersachsen.de" - - s3: - enabled: false - - auth: - # Provide the accessKeyId and secret in plain values - # We recommend to use the existingSecret option instead - accessKeyId: - secretAccessKey: - - ## To avoid having sensitive credentials in your values.yaml, the preferred way is to - ## use an existing secret containing the S3 compatible access credentials. - ## Specify the name of this existing secret here. - - # if using an existing secret, use the following keys for your access key and secret. - # OPENPROJECT_FOG_CREDENTIALS_AWS__ACCESS__KEY__ID - # OPENPROJECT_FOG_CREDENTIALS_AWS__SECRET__ACCESS__KEY - - # note there are double underscores on these keys - existingSecret: - - region: - bucketName: - - ## Remove or leave empty to use default AWS S3 endpoint - # - endpoint: - host: - port: - pathStyle: false - signatureVersion: 4 - useIamProfile: false - # Some providers do not properly support signature v4 streaming (e.g. Scaleway) - enableSignatureV4Streaming: true - - ## If enabled, upload files directly to S3 from the browser instead of going through OpenProject. - ## May not be supported by providers other than AWS S3 itself. - ## - ## Ref.: https://www.openproject.org/docs/installation-and-operations/configuration/#direct-uploads - # - directUploads: true - ## Configure PostgreSQL settings. # postgresql: