# Allure TestOps release management
# Update this to install different release – check the release notes
# Release notes: https://docs.qameta.io/allure-testops/release-notes/
ALLURE_VERSION=4.18.0

# External Network Settings
# you need to update these settings accordingly to your network set up for Allure TestOps

ALLURE_HOST=allure.io
ALLURE_INSTANCE_PORT=80

ALLURE_PROTO=http
ALLURE_SESSION_DURATION=57600

# Update this parameter. It's important for interactions with other systems.
TZ="Europe/London"

# Standard Admin's Login name. This user allows you restoring the access to Allure TestOps
ALLURE_ADMIN=admin
# Update this before deployment
ALLURE_ADMIN_PASS=admin

# Crypto parameters
# Update this by generating a secret e.g. like `openssl rand -base64 16` and put the output here
ALLURE_JWT_SECRET=<SET_YOUR_SECRET_HERE>

# Update this. This is to be set once before deployment and you need to keep this password in a safe place.
# This parameter's value is used to encrypt sensitive data in the database. Losing this will require re-creation of all sensitive data.
ALLURE_CRYPTO_PASSWORD=<SET_YOUR_PASSWORD_HERE>

# Auto adding self signing SSL to JKS
## TLS_ENDPOINTS=ldaps.example.com:636,rabbit.example.com:5672
## TLS_DB_ENDPOINTS=db.example.com:5432

# TLS
ALLURE_SECURE_COOKIE=false

# Registry Settings
ALLURE_REGISTRY=reg.qatools.ru
ALLURE_SLUG=allure-testops

# Gateway
ALLURE_GATEWAY_PORT=8080
ALLURE_REDIS_HOST=redis
ALLURE_REDIS_PORT=6379
ALLURE_REDIS_PASS=Y5ZBqrcb68WKA9ZZ

# UAA
ALLURE_UAA_SERVICE_NAME=allure-uaa-service
ALLURE_UAA_CONTEXT_PATH=/uaa
ALLURE_UAA_DB_HOST=db.example.com
ALLURE_UAA_DB_NAME=uaa
ALLURE_UAA_DB_USERNAME=uaa
ALLURE_UAA_DB_PASS=CjAXjUav3eh3cmWk
ALLURE_UAA_PORT=8082
ALLURE_UAA_DB_PORT=5432

# UAA user registration management
ALLURE_REGISTRATION_AUTOAPPROVE=false
ALLURE_REGISTRATION_ENABLED=false
ALLURE_REGISTRATION_DEFAULT_ROLE=ROLE_AUDITOR

## OIDC
# During client creation in Google/Github/Keycloak... set callback url https://${ALLURE_HOST}/login/oauth2/code/allure
OIDC_CLIENT_NAME=Google
OIDC_SCOPES=openid,email,profile
OIDC_ISSUER_URI=https://accounts.google.com
# When new user created with OIDC, this attribute will be used as allure username
OIDC_USERNAME_ATTRIBUTE=email
OIDC_CLIENT_ID=<obtain one from auth provider>
OIDC_CLIENT_SECRET=<obtain one from auth provider>

# Report
ALLURE_REPORT_SERVICE_NAME=allure-report-service
ALLURE_REPORT_CONTEXT_PATH=/rs
ALLURE_REPORT_DB_HOST=db.example.com
ALLURE_REPORT_DB_NAME=report
ALLURE_REPORT_DB_USERNAME=report
ALLURE_REPORT_DB_PASS=GnNc9QQcLzZfhVNn
ALLURE_REPORT_PORT=8081
ALLURE_REPORT_DB_PORT=5432
ALLURE_RABBIT_HOST=rabbitmq
ALLURE_RABBIT_PORT=5672
ALLURE_RABBIT_USER=allure
ALLURE_RABBIT_PASS=wNaxbX7wEhqA6ZDQ

# S3
# This variable is responsible for proxy S3 type (azure - for microsoft Azure, gcs - Google Cloud, s3 - for the rest of providers)
ALLURE_S3_PROVIDER=s3
ALLURE_S3_URL=https://<your_S3_provider_API_endpoint_here>
ALLURE_S3_BUCKET=allure-testops
ALLURE_S3_REGION=fra1
ALLURE_S3_ACCESS_KEY=<your_access_key>
ALLURE_S3_SECRET_KEY=<your_secret_key>
# Do not change it, because it's Minio's parameter, not external S3's
ALLURE_S3_PATHSTYLE=true

RABBIT_ERLANG_COOKIE=fTwP5LxRVjZ9XJkyWmJSKR5hPDWMjkQx
