Skip to content

All versions since 2.5.1

2.5.1

API version: 11.0.1

Fixed

  • set_tags and uploads with tags= accept tag values that are not ISO 8601 timestamps, such as Version=1.7.0, against JMA 2.8.2 and later. Earlier JMA versions read such a value as a date (1.7.0 as 2000-01-07) and rejected it with 400 “Detected timestamp without defining time zone”. The fix is in JMA; this package is unchanged apart from integration tests for it.

2.6.0

API version: 11.1.0

Added

  • 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.

2.6.1 Latest

API version: 11.1.0

Fixed

  • Published to PyPI. 2.6.0 reached only the internal package feed: its release pipeline failed before the PyPI upload. 2.6.1 contains the same code, so its changes are those listed under 2.6.0 below; use 2.6.1 instead of 2.6.0.