output now based upon raw input not effective input

[kbrock]

Context

// raw input
{
  "title": "Numbers to add",
  "numbers": { "val1": 3, "val2": 4 }
}

// result
7

// state
"InputPath": "$.numbers",
"ResultPath": "$.sum"

Before

// raw output:
{
  "val1": 3,
  "val2": 4,
  "sum": 7
}

After

// raw output:
{
  "title": "Numbers to add",
  "numbers": { "val1": 3, "val2": 4 },
  "sum": 7
}

refs:

• https://states-language.net/#inputoutput-processing-examples
• https://docs.aws.amazon.com/step-functions/latest/dg/input-output-example.html

[Fryguy]

Will this break any of our existing workflows like the ones in workflows-examples, or the new ootb ones?

[kbrock]

update:

• fixed spec title
• cops: fixed indentation

[miq-bot]

Checked commits https://github.com/kbrock/floe/compare/53665201fe6812367818fda5394d8881942dfe63~...933eba165b6bbc33a5275553e2b748013ec7bb53 with ruby 2.7.8, rubocop 1.56.3, haml-lint 0.51.0, and yamllint 3 files checked, 0 offenses detected Everything looks fine. :+1:

[kbrock]

Searched through https://github.com/search?q=org%3AManageIQ%20path%3A*.asl&type=code (8 files)

and for agrare, fryguy

We don't use InputPath at all. so this should no affect us.

/cc @agrare - do you see any change that may be introduced if we are not using InputPath here?

That is probably why the bug has not been discovered yet

[agrare]

@kbrock yeah agreed I don't see any use of InputPath in our existing examples