Skip to content

_v1: expose a step-script deserializer (no way to decode a bare StepScript) #334

Description

@seant-aws

Gap

The _openjd_rs binding exposes deserialize_step, which requires a full named step object. There is no entry point to deserialize a bare step script.

Consequence

Callers that hold a StepScript (e.g. the deadline-cloud-worker-agent's RustSessionRuntime adapter in aws-deadline/deadline-cloud-worker-agent#1002) must fabricate a synthetic wrapper — {"name": "Placeholder", "script": ...} — and pull .script off the deserialized step. Functional, but the synthetic name can leak into Rust-side validation error messages and confuse whoever reads the session log.

Proposal

Expose a deserialize_step_script-style function (binding and/or crate) that decodes a bare script object directly.

Related: #332 (run-task-without-session-env capability for the same adapter).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions