Overview - Flipt

Configuration precedence is as follows:

Environment Variables
Configuration File

Configuration File

The default way that Flipt is configured is with the use of a configuration file default.yml. This file is read when Flipt starts up and configures several important properties for the server.

You can generate a default configuration file by running flipt config init.

The server will check in a few different locations for server configuration (in order):

--config flag as an override
{{ USER_CONFIG_DIR }}/flipt/config.yml (the USER_CONFIG_DIR value is based on your architecture and specified in the Go documentation)
/etc/flipt/config/default.yml

We provide both a JSON schema and a Cue schema that you can use to validate your configuration file and its properties.

You can edit any of these properties to your liking, and on restart, Flipt will pick up the new changes.

Environment Substitution and Secret References

The configuration file supports both environment variable substitution and secret references.

Environment Variables

You can use environment variables in your configuration file with the ${env:VARIABLE_NAME} syntax. For example:

authentication:
  required: ${env:FLIPT_CUSTOM_AUTH_REQUIRED}

This will replace ${env:FLIPT_CUSTOM_AUTH_REQUIRED} with the value of the FLIPT_CUSTOM_AUTH_REQUIRED environment variable.

The v1 syntax ${VARIABLE_NAME} is not supported in v2. You must use the explicit ${env:VARIABLE_NAME} format.

Secret References

You can also reference secrets from configured secret providers using the ${secret:provider:path:key} syntax:

server:
  cert_file: ${secret:file:tls-cert} # Reference to file provider secret
  cert_key: ${secret:vault:tls/certs:private-key} # Reference to Vault secret

Combined Usage

You can combine environment variables and secret references in the same configuration:

authentication:
  methods:
    oidc:
      providers:
        google:
          client_id: ${env:GOOGLE_CLIENT_ID} # Environment variable
          client_secret: ${secret:vault:auth/oidc:client_secret} # Secret reference

This can be used to provide sensitive information to Flipt without storing it in the configuration file. For example, you can use environment variables to store the database URL, API keys, or other sensitive information without having to conform to the pre-defined Flipt environment variable format.

Remote Configuration

Flipt supports fetching configuration from a remote source. This is useful for managing configuration across multiple instances of Flipt. The remote configuration source can be a URL to a configuration file stored in one of the following object storage services:

S3 (e.g.: s3://bucket-name/path/to/config.yml)
Azure Blob Storage (e.g.: azblob://container-name/path/to/config.yml)
Google Cloud Storage (e.g.: googlecloud://bucket-name/path/to/config.yml)

To load Flipt configuration from a remote source, replace the config.yml file with the URL to the remote configuration file in the --config flag when starting the server.

flipt server --config s3://bucket-name/path/to/config.yml

For authenticating with the object storage service, you can use the following environment variables depending on the service:

AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
AZURE_STORAGE_ACCOUNT and AZURE_STORAGE_KEY or AZURE_CLIENT_ID, AZURE_TENANT_ID, and AZURE_CLIENT_SECRET
GOOGLE_APPLICATION_CREDENTIALS

Environment Variables

All options in the configuration file can be overridden using environment variables using the syntax:

FLIPT_<SectionName>_<KeyName>

Environment variables MUST have FLIPT_ prefix and be in UPPER_SNAKE_CASE format.

Using environment variables to override defaults is especially helpful when running with Docker.

Keys should be uppercase and . should be replaced by _. For example, given these configuration settings:

server:
  grpc_port: 9000

You can override them using:

export FLIPT_SERVER_GRPC_PORT=9001

Multiple Values

Some configuration options can have a list of values. For example, the cors.allowed_origins option can have multiple origins. In this case, you can use a space separated list of values for the environment variable override:

export FLIPT_CORS_ALLOWED_ORIGINS="http://localhost:3000 http://localhost:3001"

Configuration Parameters

The following sections group related configuration options for easier navigation:

Core Server Setup - Essential configuration to get Flipt running
Security & Access Control - Authentication, authorization, and security settings
Observability & Operations - Monitoring, logging, and analytics
Additional Settings - Optional features and enhancements

Core Server Setup

Server

Server configuration controls how Flipt listens for and serves HTTP, HTTPS, and gRPC connections.

Property	Description	Default	Since
server.protocol	http or https	http	v2.0.0
server.host	The host address on which to serve the Flipt application	0.0.0.0	v2.0.0
server.http_port	The HTTP port on which to serve the Flipt REST API and UI	8080	v2.0.0
server.https_port	The HTTPS port on which to serve the Flipt REST API and UI	443	v2.0.0
server.grpc_port	The port on which to serve the Flipt GRPC server	9000	v2.0.0
server.grpc_conn_max_idle_time	Maximum amount of time a GRPC connection can be idle	unlimited	v2.0.0
server.grpc_conn_max_age	Maximum amount of time a GRPC connection can live	unlimited	v2.0.0
server.grpc_conn_max_age_grace	Maximum amount of time a GRPC connection can live for outstanding RPCs after exceeding `grpc_conn_max_age`	unlimited	v2.0.0
server.cert_file	Path to the certificate file (if protocol is set to https)		v2.0.0
server.cert_key	Path to the certificate key file (if protocol is set to https)		v2.0.0

Storage

Storage configuration defines where and how Flipt persists feature flag data, including local and remote Git repositories.

Property	Description	Default	Since
storage.[id].name	The canonical name of the storage instance	default	v2.0.0
storage.[id].backend.type	The type of backend to use (options: memory, local)	memory	v2.0.0
storage.[id].backend.path	The path to the local storage directory for git backend	temporary directory	v2.0.0
storage.[id].remote	The remote URL to sync storage to/from		v2.0.0
storage.[id].branch	The branch to use for git backend	main	v2.0.0
storage.[id].poll_interval	The interval to poll the git repository and ref for changes	30s	v2.0.0
storage.[id].ca_cert_bytes	The CA certificate bytes for the remote URL		v2.0.0
storage.[id].ca_cert_path	The CA certificate path for the remote URL		v2.0.0
storage.[id].insecure_skip_tls	Skip verifying the server’s certificate chain (avoid in production)	false	v2.0.0
storage.[id].fetch_policy	Policy for handling connection issues when fetching from remote Git (strict, lenient)	strict	v2.3.0
storage.[id].credentials	The id of the credentials to use for the remote URL		v2.0.0

Commit Signing

Property	Description	Default	Since
storage.[id].signature.enabled	Enable or disable commit signing	false	v2.0.0
storage.[id].signature.type	Signature type (currently only “gpg” supported)	“gpg”	v2.0.0
storage.[id].signature.name	Name to use in Git commits		v2.0.0
storage.[id].signature.email	Email to use in Git commits		v2.0.0
storage.[id].signature.key_id	GPG key ID for identification		v2.0.0
storage.[id].signature.key_ref.provider	Secrets provider name for GPG private key		v2.0.0
storage.[id].signature.key_ref.path	Path to secret in provider		v2.0.0
storage.[id].signature.key_ref.key	Key name within the secret		v2.0.0

Environments

Environments configuration allows you to create isolated feature flag namespaces with separate storage backends.

Property	Description	Default	Since
environments.[id].name	The canonical name of the environment	default	v2.0.0
environments.[id].default	Whether the environment is the default environment	false	v2.0.0
environments.[id].storage	The id of the storage to use for the environment		v2.0.0
environments.[id].directory	The directory to use for the environment with the given storage		v2.0.0

Source Control Management

Property	Description	Since
environments.[id].scm.type	The type of SCM provider to use (options: github, gitlab, bitbucket, azure, gitea)	v2.0.0
environments.[id].scm.api_url	The API URL of the SCM provider to use (optional)	v2.0.0
environments.[id].scm.credentials	The id of the credentials to use for the SCM provider	v2.0.0

User Interface

User interface configuration customizes the appearance and behavior of the Flipt web UI.

Property	Description	Default	Since
ui.default_theme	Sets the default UI theme for users	system	v2.0.0
ui.topbar.color	Sets the color of the topbar		v2.0.0

CORS

Cross-Origin Resource Sharing (CORS) configuration allows web applications from different domains to access Flipt’s API.

Property	Description	Default	Since
cors.enabled	Enable CORS support	false	v2.0.0
cors.allowed_origins	Sets Access-Control-Allow-Origin header on server	”*” (all domains)	v2.0.0
cors.allowed_headers	Sets Access-Control-Allow-Headers header on server	”*” (all headers)	v2.0.0

CORS Troubleshooting

If you’re experiencing CORS issues with browser-based applications (such as Vue, React, or Angular), simply setting cors.enabled: true may not be sufficient. Browsers can be strict about CORS policies, and you may need to explicitly configure the allowed origins and other options. Common Issue: Browser applications receive CORS errors even when cors.enabled: true is set. Solution: Configure explicit CORS settings instead of relying on the wildcard defaults:

cors:
  enabled: true
  allowed_origins:
    - http://localhost:3000 # React development server
    - http://localhost:5173 # Vite development server
    - https://yourapp.com # Production domain
  allowed_headers:
    - Content-Type
    - Authorization
    - X-Requested-With
    - x-flipt-environment

When using client-side SDKs like the Flipt JavaScript SDK, make sure to include your application’s origin in the allowed_origins list and include any custom headers your application sends.

Security & Access Control

Authentication

Authentication configuration controls how users and systems authenticate with Flipt, supporting multiple methods including OIDC, GitHub, JWT, and static tokens.

Authentication is configured slightly differently in v2 compared to v1. See the Authentication documentation for more details.

Property	Description	Default	Since
authentication.required	Enable or disable authentication validation on requests	false	v2.0.0
authentication.exclude.evaluation	Exclude authentication for /evaluation/v1 API prefix	false	v2.0.0
authentication.exclude.ofrep	Exclude authentication for /ofrep API prefix	false	v2.0.0

Authentication Session

Property	Description	Default	Since
authentication.session.domain	Public domain on which Flipt instance is hosted		v2.0.0
authentication.session.secure	Configures the `Secure` property on created session cookies	false	v2.0.0
authentication.session.token_lifetime	Configures the lifetime of the session token (login duration)	24h	v2.0.0
authentication.session.state_lifetime	Configures the lifetime of state parameters during OAuth flow	10m	v2.0.0
authentication.session.csrf.key	Secret credential used to sign CSRF prevention tokens		v2.0.0
authentication.session.csrf.secure	Enable secure CSRF token enforcement	false	v2.0.0

Authentication Session Storage

Property	Description	Default	Since
authentication.session.storage.type	The type of storage to use for session storage (memory, redis)	memory	v2.0.0
authentication.session.storage.cleanup.grace_period	The grace period for the cleanup of expired sessions	30m	v2.0.0

Authentication Session Storage: Redis

Property	Description	Default	Since
authentication.session.storage.redis.mode	Required Redis mode: `single` or `cluster`	single	v2.0.0
authentication.session.storage.redis.host	Host to access the Redis database	localhost	v2.0.0
authentication.session.storage.redis.port	Port to access the Redis database	6379	v2.0.0
authentication.session.storage.redis.db	Redis database to use	0	v2.0.0
authentication.session.storage.redis.username	Username to access the Redis database		v2.0.0
authentication.session.storage.redis.password	Password to access the Redis database		v2.0.0
authentication.session.storage.redis.require_tls	Require TLS to access the Redis database	false	v2.0.0
authentication.session.storage.redis.pool_size	Max number of socket connections per CPU	10	v2.0.0
authentication.session.storage.redis.min_idle_conn	Minimum number of idle connections in the pool	0	v2.0.0
authentication.session.storage.redis.conn_max_idle_time	Maximum amount of time a connection can be idle	30m	v2.0.0
authentication.session.storage.redis.net_timeout	Network timeout for Redis connections	0	v2.0.0
authentication.session.storage.redis.ca_cert_path	Path to custom certificate authority (CA) certificate		v2.0.0
authentication.session.storage.redis.ca_cert_bytes	(Alternative) Raw certificate authority (CA) certificate bytes		v2.0.0
authentication.session.storage.redis.insecure_skip_tls	Skip verifying the server’s certificate chain (avoid in production)	false	v2.0.0

Authentication Methods: Static Token

Property	Description	Default	Since
authentication.methods.token.enabled	Enable static token authentication	false	v2.0.0
authentication.methods.token.tokens	List of static tokens to use for authentication		v2.0.0
authentication.methods.token.tokens.[token].credential	The credential to use for the token		v2.0.0
authentication.methods.token.tokens.[token].metadata	The metadata to use for the token		v2.0.0

Authentication Methods: OIDC

Property	Description	Default	Since
authentication.methods.oidc.enabled	Enable OIDC authentication	false	v2.0.0
authentication.methods.oidc.providers.[provider].issuer_url	Provider specific OIDC issuer URL (see your providers docs)		v2.0.0
authentication.methods.oidc.providers.[provider].client_id	Provider specific OIDC client ID (see your providers docs)		v2.0.0
authentication.methods.oidc.providers.[provider].client_secret	Provider specific OIDC client secret (see your providers docs)		v2.0.0
authentication.methods.oidc.providers.[provider].redirect_address	Public URL on which this Flipt instance is reachable		v2.0.0
authentication.methods.oidc.providers.[provider].scopes	Scopes to request from the provider		v2.0.0
authentication.methods.oidc.providers.[provider].use_pkce	Enable PKCE with a cryptographic nonce for OIDC authentication	false	v2.0.0
authentication.methods.oidc.providers.[provider].algorithms	List of accepted ID token signing algorithms	[“RS256”]	v2.6.0
authentication.methods.oidc.providers.[provider].fetch_extra_user_info	Fetch additional claims from the provider’s UserInfo endpoint	false	v2.6.0
authentication.methods.oidc.providers.[provider].authorize_parameters	Extra query parameters to append to the provider authorize URL	v2.11.0
authentication.methods.oidc.providers.[provider].use_end_session_endpoint	Redirect to the provider’s end-session endpoint on logout	false	v2.11.0
authentication.methods.oidc.providers.[provider].allow_front_channel_logout	Enable OIDC front-channel logout support	false	v2.12.0
authentication.methods.oidc.email_matches	List of email addresses (regex) of users allowed to authenticate		v2.0.0

Authentication Methods: GitHub

Property	Description	Default	Since
authentication.methods.github.enabled	Enable GitHub authentication	false	v2.0.0
authentication.methods.github.client_id	GitHub client ID		v2.0.0
authentication.methods.github.client_secret	GitHub client secret		v2.0.0
authentication.methods.github.redirect_address	Public URL on which this Flipt instance is reachable		v2.0.0
authentication.methods.github.scopes	Scopes to request from GitHub		v2.0.0
authentication.methods.github.allowed_organizations	List of GitHub organizations allowed to authenticate		v2.0.0
authentication.methods.github.allowed_teams	Map of GitHub organizations to teams that users must be members of		v2.0.0
authentication.methods.github.server_url	GitHub Server URL (to support GHES)	`https://github.com`	v2.0.0
authentication.methods.github.api_url	GitHub API URL (to support GHES)	`https://api.github.com`	v2.0.0
authentication.methods.github.use_pkce	Enable PKCE for GitHub OAuth flow	false	v2.9.0

Authentication Methods: Kubernetes

Property	Description	Default	Since
authentication.methods.kubernetes.enabled	Enable Kubernetes service account token authentication	false	v2.0.0
authentication.methods.kubernetes.discovery_url	Kubernetes API server URL for OIDC configuration discovery	`https://kubernetes.default.svc.cluster.local`	v2.0.0
authentication.methods.kubernetes.ca_path	Kubernetes API CA certification path	/var/run/secrets/kubernetes.io/serviceaccount/ca.crt	v2.0.0
authentication.methods.kubernetes.service_account_token_path	Path to Flipt service account token	/var/run/secrets/kubernetes.io/serviceaccount/token	v2.0.0

Authentication Methods: JWT

Property	Description	Default	Since
authentication.methods.jwt.enabled	Enable JWT authentication	false	v2.0.0
authentication.methods.jwt.jwks_url	URL to retrieve JWKS for JWT validation		v2.0.0
authentication.methods.jwt.public_key_file	Path to public key file for JWT validation		v2.0.0
authentication.methods.jwt.validate_claims.issuer	The issuer claim to validate on JWT tokens		v2.0.0
authentication.methods.jwt.validate_claims.audiences	The audience claim (list) to validate on JWT tokens		v2.0.0
authentication.methods.jwt.validate_claims.subject	The subject claim to validate on JWT tokens		v2.0.0

Authorization

Authorization configuration enforces fine-grained access control policies to restrict operations based on user roles and permissions.

Property	Description	Default	Since
authorization.required	Enable or disable authorization validation on requests	false	v2.0.0

Authorization Backend: Local

Property	Description	Default	Since
authorization.local.policy.path	Path to the local policy file		v2.0.0
authorization.local.policy.poll_interval	Interval to poll the policy file for changes	5m	v2.0.0
authorization.local.data.path	Path to the local data file		v2.0.0
authorization.local.data.poll_interval	Interval to poll the data file for changes	30s	v2.0.0

Credentials

Credentials configuration manages authentication details for accessing remote Git repositories and SCM providers.

Property	Description	Default	Since
credentials.[id].type	The type of credentials to use (options: basic, ssh, access_token, github_app)	basic	v2.0.0

Credentials: Basic

Property	Description	Default	Since
credentials.[id].basic.username	The username to use for basic authentication		v2.0.0
credentials.[id].basic.password	The password to use for basic authentication		v2.0.0

Credentials: SSH

Property	Description	Default	Since
credentials.[id].ssh.user	The username to use for SSH authentication	git	v2.0.0
credentials.[id].ssh.password	Password used to generate the SSH key pair		v2.0.0
credentials.[id].ssh.private_key_path	Path to private key on the filesystem		v2.0.0
credentials.[id].ssh.private_key_bytes	(Alternative) Raw private key bytes		v2.0.0
credentials.[id].ssh.insecure_ignore_host_key	Skip verifying the known hosts key (avoid in production)	false	v2.0.0

Credentials: Access Token

Property	Description	Default	Since
credentials.[id].access_token	The token to use for authentication		v2.0.0

Credentials: GitHub App

Property	Description	Since
credentials.[id].github_app.client_id	The GitHub App client ID	v2.6.0
credentials.[id].github_app.installation_id	The GitHub App installation ID	v2.6.0
credentials.[id].github_app.private_key_path	Path to the GitHub App private key on the filesystem	v2.6.0
credentials.[id].github_app.private_key_bytes	(Alternative) Raw GitHub App private key bytes	v2.6.0
credentials.[id].github_app.api_url	Custom GitHub API URL (for GitHub Enterprise Server)	v2.6.0

Secrets

Secrets configuration enables integration with external secret management systems for secure credential storage. See the Secrets documentation for detailed provider setup and usage.

Property	Description	Default	Since
secrets.providers.[id].enabled	Enable or disable the secrets provider	false	v2.0.0

Secrets Provider: File

Property	Description	Default	Since
secrets.providers.file.base_path	Base directory path for storing secret files	/etc/flipt/secrets	v2.0.0

Secrets Provider: Vault

Property	Description	Default	Since
secrets.providers.vault.address	URL address of the Vault server		v2.0.0
secrets.providers.vault.auth_method	Authentication method	token	v2.0.0
secrets.providers.vault.token	Vault token for authentication		v2.0.0
secrets.providers.vault.role	Role name for authentication		v2.0.0
secrets.providers.vault.mount	Vault mount path for secrets	secret	v2.0.0
secrets.providers.vault.namespace	Vault namespace for enterprise Vault deployments		v2.0.0

Secrets Provider: AWS Secrets Manager

Property	Description	Default	Since
secrets.providers.aws.endpoint_url	Custom endpoint URL (for LocalStack or AWS-compatible services)		v2.8.0

Secrets Provider: GCP Secret Manager

Property	Description	Since
secrets.providers.gcp.project	GCP project ID	v2.8.0
secrets.providers.gcp.location	GCP region for regional secrets	v2.8.0
secrets.providers.gcp.credentials	Path to service account credentials JSON file	v2.8.0

Secrets Provider: Azure Key Vault

Property	Description	Default	Since
secrets.providers.azure.vault_url	Azure Key Vault URL (e.g., `https://my-vault.vault.azure.net/`)		v2.8.0

Observability & Operations

Logging

Logging configuration controls the format, destination, and verbosity of Flipt’s application logs.

Property	Description	Default	Since
log.level	Level at which messages are logged (debug, info, warn, error, fatal, panic)	info	v2.0.0
log.grpc_level	Level at which gRPC messages are logged (debug, info, warn, error, fatal, panic)	error	v2.0.0
log.file	File to log to instead of STDOUT		v2.0.0
log.encoding	Encoding to use for logging (json, console)	console	v2.0.0
log.keys.time	Structured logging key used when outputting log timestamp	T	v2.0.0
log.keys.level	Structured logging key used when outputting log level	L	v2.0.0
log.keys.message	Structured logging key used when outputting log message	M	v2.0.0

Logging: OTLP

Flipt v2 supports the new OpenTelemetry OTLP logging specification. To enable OTLP logging, set the OTLP_LOGS_EXPORTER environment variable

export OTLP_LOGS_EXPORTER=otlp

OpenTelemetry logging is in addition to the existing logging configuration. It does not replace the ability to log to a file or stdout/stderr.

OpenTelemetry OTLP logging is configured via the default OpenTelemetry Environment Variables. See the OpenTelemetry Environment Variables documentation for more details. For example, to configure the OTLP logging endpoint, you can set the OTEL_EXPORTER_OTLP_LOGS_ENDPOINT environment variable.

export OTEL_EXPORTER_OTLP_LOGS_ENDPOINT=http://localhost:4317

Metrics

Metrics configuration enables operational monitoring through Prometheus or OpenTelemetry exporters.

Property	Description	Default	Since
metrics.enabled	Enable metrics support	true	v2.0.0
metrics.exporter	The exporter to use (prometheus, otlp)	prometheus	v2.0.0

Metrics: OTLP

OpenTelemetry OTLP metrics are configured via the default OpenTelemetry Environment Variables. See the OpenTelemetry Environment Variables documentation for more details. For example, to configure the OTLP metrics endpoint, you can set the OTEL_EXPORTER_OTLP_METRICS_ENDPOINT environment variable.

export OTEL_EXPORTER_OTLP_METRICS_ENDPOINT=http://localhost:4317

To configure the OTLP headers, you can set the OTEL_EXPORTER_OTLP_METRICS_HEADERS environment variable.

export OTEL_EXPORTER_OTLP_METRICS_HEADERS="Authorization=Bearer <token>"

Tracing

Tracing configuration enables distributed tracing for observability and performance analysis using OpenTelemetry.

Property	Description	Default	Since
tracing.enabled	Enable tracing support	false	v2.0.0

The only supported tracing backend is OTLP.

Tracing: OTLP

OpenTelemetry OTLP tracing is configured via the default OpenTelemetry Environment Variables. See the OpenTelemetry Environment Variables documentation for more details. For example, to configure the OTLP tracing endpoint, you can set the OTEL_EXPORTER_OTLP_TRACES_ENDPOINT environment variable.

export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://localhost:4317

To configure the OTLP headers, you can set the OTEL_EXPORTER_OTLP_TRACES_HEADERS environment variable.

export OTEL_EXPORTER_OTLP_TRACES_HEADERS="Authorization=Bearer <token>"

Evaluation

Evaluation configuration controls feature flag evaluation behavior and related API response data.

Property	Description	Default	Since
evaluation.include_flag_metadata	Include flag metadata in ListFlags API response objects	false	v2.3.0

Flag metadata can contain operator-defined data. Keep evaluation.include_flag_metadata disabled unless clients that call ListFlags should receive that metadata.

Analytics

Analytics configuration enables collection and export of feature flag evaluation metrics to external analytics systems.

Property	Description	Default	Since
analytics.buffer.flush_period	Duration to wait before sending events to sinks	10s	v2.0.0

Analytics: Clickhouse

Property	Description	Default	Since
analytics.storage.clickhouse.enabled	Enable Clickhouse support	false	v2.0.0
analytics.storage.clickhouse.url	URL to connect to clickhouse server		v2.0.0

Analytics: Prometheus

Property	Description	Default	Since
analytics.storage.prometheus.enabled	Enable Prometheus support	false	v2.0.0
analytics.storage.prometheus.url	URL to connect to prometheus server		v2.0.0
analytics.storage.prometheus.headers	Additional headers to send with Prometheus requests (map[string]string)		v2.0.0
analytics.storage.prometheus.sigv4.enabled	Enable Prometheus SigV4 suppport	false	v2.7.0
analytics.storage.prometheus.sigv4.region	AWS region for SigV4 signing (for Amazon Managed Service for Prometheus)		v2.7.0
analytics.storage.prometheus.sigv4.access_key	AWS access key ID		v2.7.0
analytics.storage.prometheus.sigv4.secret_key	AWS secret access key		v2.7.0
analytics.storage.prometheus.sigv4.profile	AWS credentials profile name		v2.7.0
analytics.storage.prometheus.sigv4.role_arn	ARN of an IAM role to assume for authentication		v2.7.0

Additional Settings

Templates

Templates configuration customizes the generated commit messages and merge proposal content that Flipt creates for Git-backed workflows. Template values use Go text/template syntax.

Property	Description	Since
templates.commit_message	Commit message template for UI-created changes	v2.5.0
templates.proposal_title	Merge proposal title template	v2.5.0
templates.proposal_body	Merge proposal body template	v2.5.0

config.yaml

templates:
  commit_message: "{{ (index .Changes 0) }} [skip ci]"
  proposal_title: "Flipt: Update {{.Base.Ref}} from {{.Branch.Ref}}"
  proposal_body: |
    This proposal updates Flipt resources.

    Source branch: {{.Branch.Ref}}
    Target branch: {{.Base.Ref}}

Server-wide templates override Flipt’s built-in defaults. Repository-level templates in flipt.yaml or flipt.yml override server-wide templates for that repository.

Flipt validates configured templates when it loads the configuration. Invalid server-wide templates prevent the configuration from loading.

License

License configuration enables Pro features by providing a valid license key.

Property	Description	Default	Since
license.key	The license key to use for the license (required for Pro features)		v2.0.0
license.machine_id	Stable machine fingerprint override for container environments		v2.8.0

A license is only required for Pro features. See the Licensing documentation for more information.

Meta & Diagnostics

Meta configuration controls Flipt’s internal behavior including update checks, telemetry, and diagnostic endpoints.

Property	Description	Default	Since
meta.check_for_updates	Enable check for newer versions of Flipt on startup	true	v2.0.0
meta.telemetry_enabled	Enable anonymous telemetry data (see Telemetry)	true	v2.0.0
meta.state_directory	Directory on the host to store local state	$HOME/.config/flipt	v2.0.0
diagnostics.profiling.enabled	Enable profiling endpoints for pprof	false	v2.0.0

Changed in v2.10.0: diagnostics.profiling.enabled now defaults to false. If you rely on pprof endpoints, explicitly set it to true in your configuration.

Deprecations

From time to time configuration options will need to be deprecated and eventually removed. Deprecated configuration options will be removed after ~6 months from the time they were deprecated. All deprecated configuration options will be removed from the documentation, however, they will still work as expected until they’re removed. A warning will be logged in the Flipt logs when a deprecated configuration option is used. All deprecated options are listed in the DEPRECATIONS file in the Flipt repository as well as the CHANGELOG.

​Configuration File

​Environment Substitution and Secret References

​Environment Variables

​Secret References

​Combined Usage

​Remote Configuration

​Environment Variables

​Multiple Values

​Configuration Parameters

​Core Server Setup

​Server

​Storage

​Commit Signing

​Environments

​Source Control Management

​User Interface

​CORS

​CORS Troubleshooting

​Security & Access Control

​Authentication

​Authentication Session

​Authentication Session Storage

​Authentication Session Storage: Redis

​Authentication Methods: Static Token

​Authentication Methods: OIDC

​Authentication Methods: GitHub

​Authentication Methods: Kubernetes

​Authentication Methods: JWT

​Authorization

​Authorization Backend: Local

​Credentials

​Credentials: Basic

​Credentials: SSH

​Credentials: Access Token

​Credentials: GitHub App

​Secrets

​Secrets Provider: File

​Secrets Provider: Vault

​Secrets Provider: AWS Secrets Manager

​Secrets Provider: GCP Secret Manager

​Secrets Provider: Azure Key Vault

​Observability & Operations

​Logging

​Logging: OTLP

​Metrics

​Metrics: OTLP

​Tracing

​Tracing: OTLP

​Evaluation

​Analytics

​Analytics: Clickhouse

​Analytics: Prometheus

​Additional Settings

​Templates

​License

​Meta & Diagnostics

​Deprecations

Configuration File

Environment Substitution and Secret References

Environment Variables

Secret References

Combined Usage

Remote Configuration

Environment Variables

Multiple Values

Configuration Parameters

Core Server Setup

Server

Storage

Commit Signing

Environments

Source Control Management

User Interface

CORS

CORS Troubleshooting

Security & Access Control

Authentication

Authentication Session

Authentication Session Storage

Authentication Session Storage: Redis

Authentication Methods: Static Token

Authentication Methods: OIDC

Authentication Methods: GitHub

Authentication Methods: Kubernetes

Authentication Methods: JWT

Authorization

Authorization Backend: Local

Credentials

Credentials: Basic

Credentials: SSH

Credentials: Access Token

Credentials: GitHub App

Secrets

Secrets Provider: File

Secrets Provider: Vault

Secrets Provider: AWS Secrets Manager

Secrets Provider: GCP Secret Manager

Secrets Provider: Azure Key Vault

Observability & Operations

Logging

Logging: OTLP

Metrics

Metrics: OTLP

Tracing

Tracing: OTLP

Evaluation

Analytics

Analytics: Clickhouse

Analytics: Prometheus

Additional Settings

Templates

License

Meta & Diagnostics

Deprecations