# rasax specific settings
rasax:
    enabled: true
    # initialUser is the user which is created upon the initial start of Rasa Enterprise
    url: "http://rasa-x-rasa-x.rasax.svc:5002"
    initialUser:
        # username specifies a name of this user - defaults to "admin"
        username: "admin"
        # password for the Rasa Enterprise user
        password: "chat_bot-@34hiB7T"
    # passwordSalt Rasa X uses to salt the user passwords
    passwordSalt: "chat_bot-@34hiB7T"
    # token Rasa X accepts as authentication token from other Rasa services
    token: "chat_bot-@34hiB7T"
    # jwtSecret which is used to sign the jwtTokens of the users
    jwtSecret: "chat_bot-@34hiB7T"
    tag: "0.42.6" #the type of rasax that you want to deploy
    hostNetwork: true
    service:
       type: NodePort
       port: 5002
       targetPort: 5002
       nodePort: 30005
    endpoints:
      # In order to send messages to the same
      # event broker as Rasa X/Enterprise does we can pass
      # a custom configuration.
      eventBroker:
        type: "pika"
        url: "rasa-x-rabbit.rasax.svc"
        username: "user"
        password: ${RABBITMQ_PASSWORD}
        port: 5672
        queues:
          - "rasa_production_events"

      # Use Rasa X as a model server
      models:
        enabled: true
        # User Rasa X/Enterprise token
        # If you use the Rasa X Helm chart you can set a token by using the `rasax.token` parameter
        # See: https://github.com/RasaHQ/rasa-x-helm/blob/main/charts/rasa-x/values.yaml#L22
        token: "chat_bot-@34hiB7T"
        waitTimeBetweenPulls: 20
        useRasaXasModelServer:
          enabled: true
          # -- The tag of the model that should be pulled from Rasa X/Enterprise
          tag: "production"
extraEnv:
  # The configuration for an event broker uses environment variables, thus
  # you have to pass extra environment variables that read values from
  # the rasa-x-rabbit secret.
  - name: "RABBITMQ_PASSWORD"
    valueFrom:
      secretKeyRef:
        name: rasa-x-rabbit
        key: rabbitmq-password

# rasa: Settings common for all Rasa containers
rasa:
    # token Rasa accepts as authentication token from other Rasa services
    token: "chat_chat_bot-@34hiB7T--bot-@34hiB7T"
    command: "rasa run"

    rasaWorker:
      type: Load


# RabbitMQ specific settings
rabbitmq:
    # rabbitmq settings of the subchart
    auth:
        # password which is used for the authentication
        password: "chat_bot-34hiB7T"
    service:
        type: "LoadBalancer"
# global settings of the used subcharts
global:
    # postgresql: global settings of the postgresql subchart
    postgresql:
        # postgresqlPassword is the password which is used when the postgresqlUsername equals "postgres"
        postgresqlPassword: "ch-chat_bot-@34hiB7T-at_bot-@34hiB7T"
    # redis: global settings of the redis subchart
    redis:
        # password to use in case there no external secret was provided
        password: "-@34hiB7T-at_bo"
# rasa: Settings common for all Rasa containers
rasa:
    # Rasa Open Source configuration you did in previous steps
    version: "2.8.14"
    # tag refers to the Rasa image tag
    tag: "2.8.14-full"
app:
  install: true
  name: "atwine/rasa-action-server"
  tag: "sixth_commit"


## Please look at this to understand more:
#https://stackoverflow.com/questions/41509439/whats-the-difference-between-clusterip-nodeport-and-loadbalancer-service-types
#- you will need to know the differences in exposing the services to different exposures.