advanced.values.yaml

---
################################################################################
## FOSSA on-premises Helm values (advanced)
################################################################################
global:
  # Environment name (used for logging).
  environment: production
  # The FOSSA image credentials that you were given by your account manager.
  imageCredentials:
    username:
    password:

# 64-character hexadecimal string, used to encrypt application secrets. Please
# pick something more random than the default value.
encryptionSecret: 0000000000000000000000000000000000000000000000000000000000000000

# The URL hostname and port that the FOSSA web server should listen on.
#
# This hostname must be accessible to users, and you'll need to configure a DNS
# record for this hostname.
hostname: &core-web-hostname fossa.local
port: 80

# Postgres database for the FOSSA web application.
postgres:
  # Database name to use for the FOSSA web application's database.
  database: fossa

  # Username for the database user. If using self-hosted Postgres, this will be
  # the username of the database user that FOSSA creates automatically.
  username:
  # Password for the database user. If using self-hosted Postgres, this will be
  # the password of the database user that FOSSA creates automatically.
  password:

  # If using self-hosted Postgres, set to true. Helm will create and manage a
  # Postgres database as part of this installation. `provisionInstance: true` is
  # mutually exclusive with setting `host`.
  provisionInstance: false
  # If using external managed hosting for Postgres, provide the URL here. Leave
  # blank otherwise. If set, mutually exclusive with `provisionInstance: true`.
  host:

# Object storage for the FOSSA web application.
storage:
  # Access key and secret key for S3 or MinIO.
  auth:
    accessKey:
    secretKey:
  # The bucket name to store FOSSA web application files in.
  bucket: files-fossa.domain.com

  # The endpoint of the S3 service, including protocol. If using S3, this should
  # be an S3 endpoint. If using MinIO, this should be one of the values of
  # `ingress.hosts[]`.
  #
  # Example: https://s3.us-east-2.amazonaws.com
  endpoint:
  # The S3 region. Only required if using S3. Leave empty if using MinIO.
  region:

  # Set to true if using MinIO.
  provisionInstance: false
  # Ingress configuration for MinIO. Configure only if
  # `provisionInstance: true`.
  ingress:
    # Set to true when `provisionInstance: true`.
    enabled: false
    # Set the hostname that MinIO will be accessible at. This should be the
    # hostname of the URL you use in the `endpoint` value.
    #
    # This hostname must be accessible to users, and you'll need to configure a
    # DNS record for this hostname if `provisionInstance: true`.
    hosts:
      - minio-core.local
    # TLS configurations. See your ingress controller for documentation.
    annotations: {}
    tls: []

# Job queue for FOSSA web application. This is always self-hosted.
faktory:
  # Set a password for the self-hosted instance.
  auth:
    password:
  # This configures ingress access for the web dashboard. You probably want to
  # leave this on, although you can turn it off if you need to.
  ui:
    ingress:
      enabled: true
      # The hostname of the URL at which the job queue's web dashboard will be
      # accessible.
      hosts:
        - faktory-core.local
      # TLS configurations. See your ingress controller for documentation.
      annotations: {}
      tls: []

# Email server for FOSSA web application. This is never self-hosted.
email:
  # The address from which FOSSA will send email.
  from: [email protected]

  # SMTP server configuration.
  host: smtp.fossa.local
  port: 1025
  # Credentials for the SMTP server. Remove this section if no auth is required.
  auth:
    user: user
    pass: password

# Ingress for the FOSSA web application. This makes the FOSSA service accessible
# from outside the cluster.
ingress:
  enabled: true
  annotations: {}
  tls: []
  hosts:
    - *core-web-hostname

# Self-signed certificates configuration.
trustedCertificates:

# Configuration for Hubble, which is an internal service that FOSSA uses for
# analyzing source code.
hubble:
  # The database for Hubble. Configured the same way as the FOSSA web
  # application's database. See the FOSSA web application configuration
  # comments.
  #
  # NOTE: You can reuse the same database as the FOSSA web application here.
  # Hubble will be careful to use a separate Postgres schema.
  postgres:
    database: fossa
    username:
    password:

    provisionInstance: false
    host:

  # The object storage for Hubble. Configured almost the same way as the FOSSA
  # web application's object storage. See the FOSSA web application
  # configuration comments.
  storage:
    auth:
      secretKey:
      accessKey:
    bucket: analysis-fossa.domain.com

    endpoint: https://s3.us-east-2.amazonaws.com
    region:

    provisionInstance: false
    # Note that Hubble's object storage does not require an ingress.

  # The job queue for Hubble. Configured the same way as the FOSSA web
  # application's job queue. See the FOSSA web application configuration
  # comments.
  faktory:
    auth:
      password:
    ui:
      ingress:
        enabled: true
        hosts:
          - faktory-hubble.local

# Third-party integrations.
#
# Other providers include `google`, `slack`, and `azureRepos`. For details, see
# the reference documentation in the chart's top-level `values.yaml` file.
github: {}
  # clientId:
  # clientSecret:

enabledFeatureFlags:
  # Dependency Path in Global Issues Report
  - dependencyPathGlobalIssuesReport
  # Release Groups
  - projectGrouping
  # Disable Org Alert Banner
  - disableOrgAlertBanner
  # License Headers In Reports
  - licenseHeaderReports
  # File Path in Reports
  - filePathInReports
  # Copyright Notices in Reports
  - copyrightReports
  # Show Locators in Plaintext Reports
  - locatorsInPlainTextReports
  # Show Depth in Plaintext Reports
  - depthInPlainTextReports