Build Container Apps job configs with schedule/event triggers, container specs, secrets, init containers, and managed identity.
Build Container Apps job configs with schedule/event triggers, container specs, secrets, init containers, and managed identity.
Required Fields
nameresourceGroupenvironmentIdconfiguration.triggerTypeconfiguration.replicaTimeouttemplate.containerstemplate.containers[0].imageOutput will appear here...Build an Azure Container Apps job with a Schedule trigger (cron expression), replicaTimeout/replicaRetryLimit bounding execution, an initContainers phase that must complete before the main containers array starts, and per-secret Key Vault references each independently scoped to their own managed identity. initContainers running to completion before the main container starts is the key sequencing behavior, useful for a genuine pre-flight check (like the example's db-migration-check) that should block the actual job from running if it fails, but a slow or hanging init container directly extends the job's total wall-clock time within whatever replicaTimeout budget is configured for the whole job execution.
The builder validates that name, resourceGroup, environmentId, configuration.triggerType, configuration.replicaTimeout, template.containers, and the first container's image all resolve before accepting the JSON as a valid Container Apps job definition, the fields Azure needs to know the job's trigger, timing bounds, and what to actually run; it can't verify the referenced container registry, Key Vault secret, or managed identity resource IDs actually exist and have correct role assignments, those are only surfaced when the job actually attempts to execute.
Budget replicaTimeout to cover both the init containers phase and the main containers phase combined, not just the main workload's expected runtime, a slow pre-flight check silently eats into the time available for the actual job work.
Use separate, narrowly-scoped managed identities per credential need (registry pull versus Key Vault read) rather than one identity with both permissions, limiting what's exposed if any single identity's credentials or role assignment is ever misconfigured or compromised.
Set replicaRetryLimit to a bounded, deliberate value for any job whose failure could indicate a genuine bug rather than a transient issue, unbounded or very high retry limits on a job with a real bug just repeat the failure (and its resource cost) many times before anyone notices.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.