openreplay

History

Taha Yassine Kraiem 414a6da84d feat(api): EE-SSO include idp_tenantKey in ACS URL/path feat(helm): idp_tenantKey for chalice env vars		2022-01-21 23:04:43 +01:00
..
openreplay	fix(postgres): variable name	2021-10-21 19:44:41 +05:30
alerts.yaml	feat(api): changed alerts_build script	2022-01-10 14:44:50 +01:00
assets.yaml
chalice.yaml	feat(api): EE-SSO include idp_tenantKey in ACS URL/path	2022-01-21 23:04:43 +01:00
db.yaml
docker_registry.sh
ender.yaml
http.yaml	fix(ui) - main to dev conflicts	2021-12-04 02:19:16 +05:30
install.sh
integrations.yaml
README.md
sink.yaml
storage.yaml
utilities.yaml

README.md

Core OpenReplay application configuration folder

This folder contains configuration for core OpenReplay apps. All applications share common helm chart named openreplay which can be overridden by <application>.yaml file.

Below is a sample template.

namespace: app        # In which namespace alerts runs.
image:
  repository: rg.fr-par.scw.cloud/foss # Which image to use
  name: alerts
  pullPolicy: IfNotPresent
  tag: "latest"       # Overrides the image tag whose default is the chart appVersion.

imagePullSecrets:     
  # If needed credentials to pull the image.
  # aws-registry is created using script docker_registry.sh.
  - name: aws-registry 

service:
  type: ClusterIP
  port: 9000

resources:
  limits:
    cpu: 256m
    memory: 512Mi
  requests:
    cpu: 100m
    memory: 128Mi

# env vars for the application
env:
  ALERT_NOTIFICATION_STRING: http://chalice-openreplay.app.svc.cluster.local:8000/alerts/notifications
  CLICKHOUSE_STRING: tcp://clickhouse.db.svc.cluster.local:9000/default
  POSTGRES_STRING: postgres://postgresql.db.svc.cluster.local:5432