Skip to main content
This page lists the environment variables of the executor. Lerian SISBAJUD Mensageria environment variables lists the variables of the Mensageria. BYOC configuration essentials documents the variables that every Lerian Go service shares: server, datastores, telemetry, and plugin authentication. In the tables below, the Default / Required column shows the default value. A bold qualifier (for example Required) marks the variables you must set. — means no default. A variable marked Sensitive holds a credential or key material. Inject it from your secret manager at deploy time. Do not commit its value. MENSAGERIA_BASE_URL turns on the executor. The executor requirements below apply when it is set.

Service and runtime

The production checks require POSTGRES_PASSWORD and refuse POSTGRES_SSLMODE=disable. With STREAMING_ENABLED=true, they also require STREAMING_TLS_ENABLED=true.

Authentication

License

License Manager describes how the product checks the license.

Key management

Mensageria connection

The executor calls the execution API of the Mensageria. Integrating with Lerian SISBAJUD describes it.

Execution timing

Webhook listener

Midaz

The executor reads the Midaz connection of each institution from its configuration, not from environment variables. Operating the Lerian SISBAJUD executor describes it.

Event streaming

Values that must match the Mensageria

  • RESPONSE_DEADLINE_MARGIN. The Mensageria reads the same variable. Set the same value on both components.
  • Mutual TLS. Set MENSAGERIA_MTLS_ENABLED to the same value as SISBAJUD_EXECUTION_MTLS_ENABLED on the Mensageria. With mutual TLS on the Mensageria and off on the executor, the TLS handshake fails.
  • Executor identity. On the Mensageria, the M2M client in MENSAGERIA_CLIENT_ID holds the role br-sisbajud-executor-role. EXECUTOR_M2M_SUBJECT is the sub of the token of that client.