Shared callback secretTower and the Sidecar must hold the same
ALETYX_OIDC_CALLBACK_SECRET. Generate one and pass it to both:Local — Container
The Sidecar plus its own PostgreSQL on the same host. Substitute<your-registry> and the image tag you pull.
ALETYX_DC_TOWER_SIDECAR_URL and ALETYX_DC_TOWER_DATA_INDEX_URL (see the Tower quickstart).
Kubernetes / OpenShift
In a cluster the Sidecar is a statelessDeployment (single replica) behind its own ClusterIP Service, with no Ingress — it is reached only by Tower over the pod network. Tower addresses it by in-cluster DNS, for example:
Resource profile
The Sidecar is a JVM container; size it like Tower (heap set viaJAVA_TOOL_OPTIONS). Provision enough memory for heap, metaspace, and native overhead to avoid OOMKilled events under GC pressure. See the Tower Container Configuration for the JVM and resource guidance, which applies to the Sidecar as well.
Build a customized Sidecar
The Sidecar is a self-contained Maven project (no parent POM), so once you customize a workflow you build it on its own. Prerequisites:- A JDK and Maven.
- Access to the Aletyx Maven repository — the build resolves Aletyx artifacts (the automation BOM and Kogito add-ons) from it. Configure it in your
~/.m2/settings.xml:
Repository accessIf the Aletyx Maven repository requires authentication, add a matching
<servers> entry with <id>maven-aletyx</id> and the credentials Aletyx provides. Without the repository configured, the build cannot resolve the Aletyx automation BOM and Kogito add-ons.Next Steps
- Customize the Promotion Workflow: adapt the approval flow, then rebuild
- Configuration: the full environment-variable reference (database, callbacks, integrations)
- Git Model Versioning: enable Git push on approved promotions