Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ErrorPath not working with States.Format, despite same code working directly via AWS console #596

Open
benmoveai opened this issue Nov 2, 2023 · 0 comments

Comments

@benmoveai
Copy link

benmoveai commented Nov 2, 2023

This is a (Bug Report)

Description

States.Format() doesn't seem to work when used in the ErrorPath of a Fail task.

The following state is working as expected in the AWS console:

    "My Fail State": {
      "Type": "Fail",
      "Comment": "The comment.",
      "ErrorPath": "States.Format('job_id: {}, client_id: {}', $[0].detail.job_id, $[0].detail.client_id)",
      "Cause": "A string representing the cause"
    }

however, when translated to yaml we cannot package this - it raises an error.

The following state in yaml does not work with sls package

    My Fail State:
      Type: Fail
      Comment: "The comment."
      ErrorPath: "States.Format('job_id: {}, client_id: {}', $[0].detail.job_id, $[0].detail.client_id)"
      Cause: "A string representing the cause"

When I remove the ErrorPath sls package works correctly.
I cannot remove the double quotes around States.Format i.e.

ErrorPath: States.Format('job_id: {}, client_id: {}', $[0].detail.job_id, $[0].detail.client_id)

because then I get a cannot parse ... bad indentation of a mapping entry... error, presumably because of the curly braces.

I've also tried with:

ErrorPath: "$[0].detail.job_id"

and receive the same error

For bug reports:

  • What went wrong?
    The following error occurs when doing sls package when using an ErrorPath with States.Format()
SCHEMA_VALIDATION_FAILED: /States/Fail - My Fail State. must match exactly one schema in oneOf
  • What did you expect should have happened?
    No error should have occurred

Additional Data

  • The Plugin Version you're using:
    3.17.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant