Configuration

This page collects the runtime configuration sections and build properties Elarion reads. Most are optional with sensible defaults.

ModulesCopy Anchor Link

Feature modules are enabled by default. Disable one by name:

{
  "Modules": {
    "Clients": { "Enabled": false }
  }
}

See Modules.

SchedulerCopy Anchor Link

Read by AddElarionScheduler(IConfiguration):

{
  "Scheduler": {
    "Enabled": true,
    "MaxConcurrentExecutions": 8,
    "MaxRetainedCompletedJobs": 1024,
    "MaxMisfireCatchUpRuns": 32
  }
}

See Scheduling.

Scheduled job placeholdersCopy Anchor Link

[ScheduledJob] string properties (FixedRate, FixedDelay, Cron, Enabled, …) support Spring-style configuration placeholders, re-resolved per occurrence:

See Schedules.

Feature flagsCopy Anchor Link

Declared flags are evaluated through IFeatureFlagService. Code-defined flags ([FeatureFlag]) are answered by their resolver; the values of backend-evaluated flags ([BackendFeatureFlag]) come from the provider package the host wires.

Batteries-included config-driven flagsCopy Anchor Link

AddElarionFeatureManagement(IConfiguration) (from Elarion.FeatureFlags.FeatureManagement) wires the Microsoft.FeatureManagement OpenFeature provider behind the OpenFeature-backed IBackendFeatureFlagEvaluator, so declared backend flags read their values out of the conventional FeatureManagement configuration section:

{
  "FeatureManagement": {
    "BetaCheckout": true,
    "PricingExperiment": {
      "Variants": [
        { "Name": "control", "ConfigurationValue": "control" },
        { "Name": "treatment", "ConfigurationValue": "treatment" }
      ],
      "Allocation": {
        "DefaultWhenEnabled": "control",
        "Percentile": [
          { "Variant": "treatment", "From": 0, "To": 50 },
          { "Variant": "control", "From": 50, "To": 100 }
        ]
      },
      "EnabledFor": [ { "Name": "AlwaysOn" } ]
    }
  }
}

BetaCheckout is a boolean gate (drives a [FeatureGate("BetaCheckout")]); PricingExperiment is a variant flag whose allocated variant selects a [FeatureVariant("PricingExperiment", Variant = "treatment")] implementation.

Bring-your-own providerCopy Anchor Link

AddElarionOpenFeature() (from Elarion.FeatureFlags.OpenFeature) registers the OpenFeature-backed IBackendFeatureFlagEvaluator and takes its flag values from whatever OpenFeature provider the host registers separately (services.AddOpenFeature(b => b.AddProvider(...)) — LaunchDarkly, ConfigCat, flagd, Flagsmith, …), not from an Elarion-owned config section. It maps the explicit FeatureEvaluationContext into the OpenFeature EvaluationContext off-HTTP (targeting key plus the user id / groups / tenant), so per-user targeting works under JSON-RPC, MCP, and HTTP alike. Configure the provider per its own documentation.

See Feature flags.

JSON-RPC schema generation (MSBuild)Copy Anchor Link

Properties read by Elarion.AspNetCore.SchemaGeneration during build:

See Schema generation.

Proxy identityCopy Anchor Link

AddElarionProxyIdentity(configuration, environment) binds the ProxyIdentity section (package Elarion.AspNetCore.ProxyIdentity). Outside Development it refuses to start unless Enabled is true and the section is complete, or Fixed:Enabled is true with a Fixed:Subject.

The user switch value - (ProxyIdentityDefaults.DevelopmentSignedOutUser) signs nobody in for the request; it is reserved, so no stand-in user (Development:Subject/Email, Development:Users:*:Subject/Email) may use it.

See Proxy identity.

Current user (options, not config)Copy Anchor Link

AddElarionCurrentUser(options => …) configures claim mapping in code rather than appsettings:

See Current user.

Authorization messages (options, not config)Copy Anchor Link

AddElarionAuthorization(o => …) registers AuthorizationOptions as a plain singleton; configure it in code:

builder.Services.AddElarionAuthorization(o => o.ResourceNotFoundMessage = "Not found.");

See Authorization and Resource authorization.

Idempotency purge (options, not config)Copy Anchor Link

AddElarionIdempotencyEntityFrameworkCore<TDbContext>(configure => …) takes an optional Action<IdempotencyPurgeOptions> configured in code rather than appsettings. It tunes the background IdempotencyKeyPurgeService that reclaims expired keys:

Complementary to the per-handler [Idempotent(RetentionHours = …)], which sets how long a completed key is retained; PollingInterval sets how often the worker sweeps out keys past that retention.

See Idempotency.

Outbox (options, not config)Copy Anchor Link

AddElarionOutbox<TDbContext>(configure => …) (from Elarion.Messaging.Outbox) takes an optional Action<OutboxOptions> configured in code rather than appsettings. It tunes the durable integration-event tier and its background OutboxDeliveryService:

See Event backends.

JSON serialization (options, not config)Copy Anchor Link

Every subsystem shares one canonical JsonSerializerOptions, configured in code (not appsettings) via ConfigureElarionJson(Action<ElarionJsonOptions>). AddElarion(configuration) already contributes every enabled module's source-generated context, so most hosts configure nothing:

builder.Services.ConfigureElarionJson(o => {
    o.PropertyNamingPolicy = JsonNamingPolicy.SnakeCaseLower;   // default: CamelCase
    o.TypeInfoResolvers.Add(SomeExtraContext.Default);          // an extra source-gen context
});

See Serialization.

Unexpected errors (options, not config)Copy Anchor Link

ConfigureElarionUnexpectedErrors(o => …) (from Elarion.Abstractions) sets the answer JSON-RPC, MCP and generated [HttpEndpoint] routes give for an exception that escaped the handler pipeline. Calls accumulate; a later call overrides only the hooks it sets. Both hooks receive an UnexpectedErrorContext (Exception, Transport, Operation, the call's scoped Services); a hook that throws falls back to the default.

builder.Services.ConfigureElarionUnexpectedErrors(o =>
    o.Message = _ => "Something went wrong. Please contact support and quote the reference.");

See Unexpected errors.

Request validation (options, not config)Copy Anchor Link

AddElarionValidation(configure => …) (from Elarion.Validation) registers the default IRequestValidator over Microsoft.Extensions.Validation and takes an optional Action<ValidationOptions> configured in code rather than appsettings. It also calls AddElarionJson(); the generated per-module validation resolvers register themselves through each module's ConfigureDefaultServices, so most hosts pass nothing:

builder.Services.AddElarionValidation();

See Validation.

Handler context enrichment (options, not config)Copy Anchor Link

Every handler is wrapped in a context-enrichment decorator that is on by default — it needs no registration. AddElarionUserContextEnrichment(configure => …) (from Elarion) takes an optional Action<UserContextEnrichmentOptions> configured in code rather than appsettings; call it only to narrow the payload, opt into email, or disable the built-in user enricher:

// on by default — nothing to register; call only to change the defaults
builder.Services.AddElarionUserContextEnrichment(o => o.IncludeEmail = true);   // opt into user.email (PII)
builder.Services.AddElarionUserContextEnrichment(o => o.Enabled = false);       // disable the built-in user enricher

Contribute your own trace tags / log-scope items by registering an IHandlerContextEnricher:

builder.Services.AddElarionHandlerContextEnricher<TenantContextEnricher>();

The log-scope keys only surface if the host enables IncludeScopes on its logging exporter. See Telemetry & observability › User & request context.

Connections (options, not config)Copy Anchor Link

AddElarionConnections(options => …) (from Elarion.Connections) takes an optional Action<ElarionConnectionsOptions> configured in code rather than appsettings — kernel-wide behavior every connection adapter applies identically (per-endpoint and per-connection knobs stay on the adapters):

builder.Services.AddElarionConnections(o => o.DefaultInvokeTimeout = TimeSpan.FromSeconds(10));

The layering is per-call Timeout > DefaultInvokeTimeout > unbounded; pass Timeout.InfiniteTimeSpan per call to make a single invoke unbounded without touching the default. See Connections.

TCP endpoints (options, not config)Copy Anchor Link

Each AddElarionTcpConnectionListener/Dialer call (and each runtime Apply…) configures one endpoint in code via ElarionTcpListenerOptions/ElarionTcpDialerOptions; per-connection overrides come from the session's Settings returning TcpConnectionSettings: