Skip to main content
This page lists the environment variables of the Mensageria. Lerian SISBAJUD executor environment variables lists the variables of the executor. 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.

Service and runtime

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

Authentication

The boot accepts a missing verification key and a missing issuer only when all three conditions are true: PLUGIN_AUTH_ENABLED is true, DEPLOYMENT_MODE is local or unset, and ENV_NAME is local.

License

License Manager describes how the product checks the license. “In production” means that ENVIRONMENT_NAME is not a non-production value.

Key management

Vault (when KMS_PROVIDER=vault)

Execution API and sweeper

The executor reads orders and reports results through the execution API. Integrating with Lerian SISBAJUD describes it.

Event streaming

Response files and workers

Object storage

Lerian STA consumer

The Mensageria receives remittance files only from the events that Lerian STA publishes. The consumer uses its own broker settings, STA_STREAM_*. It does not read the STREAMING_* variables.

Lerian STA submission

Values that must match the executor

  • RESPONSE_DEADLINE_MARGIN. The executor reads the same variable. Set the same value on both components.
  • Mutual TLS. The executor has its own switch, MENSAGERIA_MTLS_ENABLED. Set it to the same value as SISBAJUD_EXECUTION_MTLS_ENABLED. With mutual TLS on the Mensageria and off on the executor, the TLS handshake fails.
  • Executor identity. The M2M client of the executor holds the role br-sisbajud-executor-role. Integrating with Lerian SISBAJUD describes its permissions.