We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
variables
Sometimes when variables are fetched from the Data Index, there is duplicated information in the response.
I'd expect simply:
"variables": { "workflowdata": { "myKey": "myValue", "mantra": "Serverless Workflow is awesome!", "greeting": "Hello World" } }
If you fetch the variables, you'll get:
"variables": { "workflowdata": { "myKey": "myValue", "mantra": "Serverless Workflow is awesome!", "greeting": "Hello World" }, "workflowdata.mantra": "Serverless Workflow is awesome!", "workflowdata.greeting": "Hello World" }
See that mantra and greeting are duplicated.
mantra
greeting
Take the Hello World workflow as an example and execute it with additional inputs, for instance:
{ "myKey": "myValue" }
uname -a
ver
No response
java -version
mvnw --version
gradlew --version
The text was updated successfully, but these errors were encountered:
fjtirado
Successfully merging a pull request may close this issue.
Describe the bug
Sometimes when
variables
are fetched from the Data Index, there is duplicated information in the response.Expected behavior
I'd expect simply:
Actual behavior
If you fetch the
variables
, you'll get:See that
mantra
andgreeting
are duplicated.How to Reproduce?
Take the Hello World workflow as an example and execute it with additional inputs, for instance:
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Kogito version or git rev (or at least Quarkus version if you are using Kogito via Quarkus platform BOM)
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: