Skip to content
Archived Docsv26.2

Configuration Reference

This page lists every supported configuration option, grouped by build-time and runtime usage.

Build-Time Configuration

These settings are read during build/compile and affect generated code or CLI wiring.

Pipeline YAML

The pipeline YAML controls global settings used by the annotation processor.

PropertyTypeDefaultDescription
transportenumGRPCGlobal transport for generated adapters (GRPC or REST).

If pipeline-config.yaml (the template configuration produced by Canvas or the template generator) is present, the build can also use it to generate protobuf definitions and orchestrator endpoints at compile time.

Orchestrator CLI (Annotation)

CLI metadata is configured on the orchestrator annotation.

Annotation AttributeTypeDefaultDescription
generateClibooleantrueEnables generation of the orchestrator CLI entrypoint.
namestring"orchestrator"CLI command name.
descriptionstring"Pipeline Orchestrator CLI"CLI command description.
versionstring"1.0.0"CLI command version.

Example:

java
@PipelineOrchestrator(
    generateCli = true,
    name = "payments-orchestrator",
    description = "CSV Payments Orchestrator CLI",
    version = "1.2.0"
)
public class OrchestratorMarker {
}

CLI input expectations:

  • --input / PIPELINE_INPUT must be a JSON object matching the input DTO.
  • --input-list / PIPELINE_INPUT_LIST must be a JSON array of input DTO objects.

Examples:

bash
./app -i '{"path":"/data/in"}'
bash
./app --input-list '[{"path":"/data/a"},{"path":"/data/b"}]'

Annotation Processor Options

Pass via maven-compiler-plugin with -A arguments.

OptionTypeDefaultDescription
-Apipeline.generatedSourcesDirpathnoneBase directory for role-specific generated sources.
-Apipeline.generatedSourcesRootpathnoneLegacy alias of pipeline.generatedSourcesDir.
-Apipeline.orchestrator.generatebooleanfalseGenerate orchestrator endpoint even without @PipelineOrchestrator. CLI generation still requires the annotation.

REST Path Overrides (Build-Time)

The annotation processor reads src/main/resources/application.properties during compilation to override REST paths:

PropertyTypeDefaultDescription
pipeline.rest.path.<ServiceName>stringnoneOverrides REST path by service name.
pipeline.rest.path.<fully.qualified.ServiceClass>stringnoneOverrides REST path by service class name.

Runtime Configuration

Prefix: pipeline

Orchestrator Client Wiring (Generated)

The annotation processor generates default client wiring for orchestrators at build time. Generated values have lower priority than explicit application.properties settings or environment variables.

To override routing or ports, set the following in application.properties:

PropertyTypeDefaultDescription
pipeline.module.<module>.hoststringnoneHost for a module (applies to all its services).
pipeline.module.<module>.portintnonePort for a module (applies to all its services).
pipeline.module.<module>.stepslistnoneComma/space-separated client names to assign.
pipeline.module.<module>.aspectslistnoneAspect names to assign (e.g. persistence).
pipeline.client.base-portint8443Base port used when assigning per-module offsets.
pipeline.client.tls-configuration-namestringnoneTLS registry name for generated clients.

Client names follow the same conventions as generated adapters:

  • regular steps: process-<service> (for example ProcessPaymentServiceprocess-payment)
  • synthetic steps: observe-<aspect>-<type>-side-effect (for example persistence + PaymentRecord)

About modules:

  • A module is a deployment/runtime group for one or more services (for example, payments-processing-svc hosting multiple steps).
  • Use module overrides when multiple services share the same runtime or when legacy layouts bundle steps together (like csv-payments).
  • Avoid module overrides if you want the default 1‑step‑per‑module layout; in that case, only override individual clients as needed.

Avoiding drift:

  • Keep server ports and orchestrator client ports aligned by sourcing them from the same pipeline.module.<module>.port or shared environment variables.
  • If you override a client endpoint directly, verify the corresponding server listens on the same host/port (especially when TLS is enabled).

If you need to override a single client endpoint, set the Quarkus property directly:

properties
quarkus.grpc.clients.<client>.host=host
quarkus.grpc.clients.<client>.port=8444
quarkus.grpc.clients.<client>.tls-configuration-name=pipeline-client
quarkus.rest-client.<client>.url=https://host:8444
quarkus.rest-client.<client>.tls-configuration-name=pipeline-client

REST Client Endpoints

REST client steps use Quarkus REST client configuration:

PropertyTypeDefaultDescription
quarkus.rest-client.<client-name>.urlstringnoneBase URL for a REST client step.

client-name is derived from the service class name in kebab-case with a trailing Service removed (for example ProcessPaymentServiceprocess-payment).

Cache Configuration

Prefix: pipeline.cache

PropertyTypeDefaultDescription
pipeline.cache.providerstringnoneCache provider name (for example redis, caffeine, memory).
pipeline.cache.provider.classstringnoneFully-qualified cache provider class name to lock selection at runtime.
pipeline.cache.policystringcache-onlyDefault cache policy (prefer-cache/return-cached, cache-only, skip-if-present, require-cache, bypass-cache).
pipeline.cache.ttldurationnoneDefault cache TTL.
pipeline.cache.caffeine.namestringpipeline-cacheCache name for the Caffeine provider.
pipeline.cache.caffeine.maximum-sizelong10000Maximum cache size for the Caffeine provider.
pipeline.cache.caffeine.expire-after-writedurationnoneExpire entries after write for the Caffeine provider.
pipeline.cache.caffeine.expire-after-accessdurationnoneExpire entries after access for the Caffeine provider.
pipeline.cache.redis.prefixstringpipeline-cache:Key prefix for Redis cache entries.

Persistence Configuration

Prefix: pipeline.persistence

PropertyTypeDefaultDescription
pipeline.persistence.duplicate-keystringfailDuplicate key policy for persistence (fail, ignore, upsert).
persistence.provider.classstringnoneFully-qualified persistence provider class name to lock selection at runtime.

Pipeline Execution

Prefix: pipeline

PropertyTypeDefaultDescription
pipeline.parallelismstringAUTOParallelism policy: SEQUENTIAL, AUTO, or PARALLEL.
pipeline.max-concurrencyinteger128Per-step maximum in-flight items when parallel execution is enabled.

Telemetry

Prefix: pipeline.telemetry

PropertyTypeDefaultDescription
pipeline.telemetry.item-input-typestringnoneFully-qualified input type used to define the item boundary (build-time only — requires rebuild to take effect).
pipeline.telemetry.item-output-typestringnoneFully-qualified output type used to define the item boundary (build-time only — requires rebuild to take effect).
pipeline.telemetry.slo.rpc-latency-msnumber1000RPC latency threshold (ms) used to emit SLO counters.
pipeline.telemetry.slo.item-throughput-per-minnumber1000Item throughput threshold (items/min) used to emit SLO counters.

Item boundary types are compiled into telemetry metadata; runtime changes do not apply unless you rebuild the project.

Kill Switches

Prefix: pipeline.kill-switch

PropertyTypeDefaultDescription
pipeline.kill-switch.retry-amplification.enabledbooleanfalseEnable retry amplification guard.
pipeline.kill-switch.retry-amplification.windowdurationPT30SEvaluation window for sustained inflight growth.
pipeline.kill-switch.retry-amplification.inflight-slope-thresholddouble10Inflight slope threshold (items/sec).
pipeline.kill-switch.retry-amplification.modestringfail-fastGuard behavior (fail-fast or log-only).
pipeline.kill-switch.retry-amplification.sustain-samplesinteger3Consecutive samples above the threshold required to trigger.

Global Defaults

Prefix: pipeline.defaults

PropertyTypeDefaultDescription
pipeline.defaults.retry-limitinteger3Max retry attempts for steps.
pipeline.defaults.retry-wait-mslong2000Base delay between retries (ms).
pipeline.defaults.recover-on-failurebooleanfalseEnables recovery behavior on failure.
pipeline.defaults.max-backofflong30000Maximum backoff delay (ms).
pipeline.defaults.jitterbooleanfalseAdds jitter to retry delays.
pipeline.defaults.backpressure-buffer-capacityinteger128Per-step backpressure buffer capacity (in items).
pipeline.defaults.backpressure-strategystringBUFFERBackpressure strategy (BUFFER or DROP).

These defaults apply to every step unless a step-level override is present.

Build-Time Validation (Annotation Processor)

These are build-time options passed to the annotation processor (not runtime config).

OptionTypeDefaultDescription
pipeline.provider.class.<name>stringnoneProvider class name to validate ordering/thread-safety hints (e.g. pipeline.provider.class.cache=...).

Per-Step Overrides

Prefix: pipeline.step."fully.qualified.StepClass"

All properties listed under pipeline.defaults.* can be overridden per step:

properties
pipeline.step."com.example.MyStep".retry-limit=7
pipeline.step."com.example.MyStep".recover-on-failure=true
pipeline.step."com.example.MyStep".backpressure-buffer-capacity=4096
pipeline.step."com.example.MyStep".backpressure-strategy=BUFFER

Startup Health Checks

PropertyTypeDefaultDescription
pipeline.health.startup-timeoutdurationPT5MMax time to wait for startup dependency health checks.