v1.3.30 — Step Functions REST-JSON aws-sdk output casing

May 6, 2026 · v1.3.30

Small but load-bearing fix on top of 1.3.29's Step Functions aws-sdk parity push.

REST-JSON output now matches the rest of the dispatcher

The Step Functions aws-sdk dispatcher has three protocol paths inside MiniStack — query, REST-XML, and REST-JSON. The query and REST-XML paths normalise output keys to MiniStack's PascalCase SFN convention via _convert_keys_to_sfn_convention. The REST-JSON path was missing that step, so successful integrations like aws-sdk:rdsdata:executeStatement exposed the raw wire keys (records, stringValue, numberOfRecordsUpdated) instead of the PascalCase the rest of the SDK surface uses.

The visible symptom: ResultSelector paths like $.Records resolved to null because the actual key in the output was records. Now REST-JSON output keys are Records, NumberOfRecordsUpdated, GeneratedFields, and StringValue — consistent with every other dispatcher in the same module:

"ObserveUser": {
  "Type": "Task",
  "Resource": "arn:aws:states:::aws-sdk:rdsdata:executeStatement",
  "Parameters": { ... },
  "ResultSelector": {
    "Records.$": "$.Records",
    "Updated.$": "$.NumberOfRecordsUpdated"
  },
  "End": true
}

Contributed by @jayjanssen.

Upgrade

docker pull ministackorg/ministack:1.3.30
docker run -d -p 4566:4566 ministackorg/ministack:1.3.30

Or pin in compose.yaml:

services:
  ministack:
    image: ministackorg/ministack:1.3.30
    ports:
      - "4566:4566"