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

Automate expression method broken in jansa and kasparov #476

Open
phospi opened this issue Apr 8, 2021 · 1 comment
Open

Automate expression method broken in jansa and kasparov #476

phospi opened this issue Apr 8, 2021 · 1 comment

Comments

@phospi
Copy link

phospi commented Apr 8, 2021

Hi,

I was checking jansa with expression methods as described in the Cloudforms / ManageIQ book [1] with user input and couldn't get it to work. It looks like variable resolution is no longer working for expression methods. Or maybe the syntax changed.

Affected versions (or what I tested):
jansa-2.20201027185742_b8d5deb
jansa-3.20210118183104_77bdc30
kasparov-1.20210203001902_15acbea

Steps to reproduce:
Follow the chapter "Expression methods" in the addendum [2]

Expected output:
Expression Method should deliver a result based on variables.

Actual result:
<None>

Additional info:
It is pretty interesting to compare the logging output in automation.log in ivanchuk and in jansa of an expression method:
Ivanchuck:
INFO -- : Invoking [expression] method [/Expression/General/my_expression_check] with inputs [{"arg1"=>"value1", "arg2"=>"foo", "arg3"=>"bar"}]

Jansa/Kasparov:
INFO -- : Invoking [expression] method [/Expression/General/my_expression_check] with inputs [{"arg1"=>"${/#dialog_my_field1}", "arg2"=>"${/#dialog_my_field2}", "arg3"=>"${/#dialog_my_field3}"}]
ERROR -- : Expression method ends

If that's important I tested expression method with tags.

Kind Regards,
phospi

Links

@phospi phospi changed the title Automate expression method broken in jansa Automate expression method broken in jansa and kasparov Apr 9, 2021
@chessbyte chessbyte transferred this issue from ManageIQ/manageiq Apr 15, 2021
@miq-bot
Copy link
Member

miq-bot commented Feb 27, 2023

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

@miq-bot miq-bot added the stale label Feb 27, 2023
@Fryguy Fryguy removed the stale label Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants