JMA Client

Version 2.6.0

Oct 19, 2026

API version: 11.1.0

ProcessingStep.configure_deployment() takes resources=ResourcesConfiguration(cpu_millicores=..., memory_mi_b=..., disk_gi_b=...) as an alternative to resource_preset=. Pass exactly one of the two, otherwise the call raises ApiException; so do values that are not greater than zero or exceed the platform’s resource ceiling. resource_preset= keeps working as before and now stands for fixed values: xsmall 250/512/3, small 500/1024/5, medium 1000/4096/10, large 3000/14336/70, xlarge 6000/28672/200, xxlarge 14000/60416/300 (millicores/MiB/GiB). The deployment of a ProcessingStep (processing_step_hco.deployment) shows cpu_millicores, memory_mi_b and disk_gi_b; resource_preset is set only when the values are exactly those of a preset. Needs JMA API 11.1.