Skip to content

clarify orchestration_save/restore sample #28

@ericrqs

Description

@ericrqs

We were confused about what orchestration_save should return and what orchestration_receive will be called with.

orchestration_save:
Should it return JSON or always this helper class? The comments mention needing a jsonpickle dependency. Is there a hidden call, is it built into the system, or is it not really used? Does jsonpickle need to be a included in the driver because of some invisible infrastructure?

It would be good to have a sample that doesn't require learning any advanced tricks and returns a pure JSON string, if that's possible. Most people would just tweak the sample string and move on.

orchestration_restore:
It was unclear when implementing the caller whether the input is supposed to be wrapped in:
{"saved_artifacts_info": {}}.

Is there some JSON infrastructure where the actual data is always wrapped in a dictionary with a single key that seems to identify the type?

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