-
Notifications
You must be signed in to change notification settings - Fork 31
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
python rule engine support + other plugin rule engines #259
Milestone
Comments
michael-conway
modified the milestones:
4.2.1.0 Mx and Compatability,
Unassigned/Pending,
4.2.1.0 Mx and Compatability Release
Sep 28, 2017
review...
|
michael-conway
added a commit
that referenced
this issue
Oct 2, 2017
michael-conway
added a commit
that referenced
this issue
Oct 2, 2017
michael-conway
added a commit
that referenced
this issue
Oct 2, 2017
michael-conway
added a commit
that referenced
this issue
Oct 2, 2017
example python user submitted rules |
michael-conway
changed the title
add enum to indicate rule executing on chosen rule engine
python rule engine support + other plugin rule engines
Oct 2, 2017
example user submitted python rule https://irods.org/2016/07/writing-rules-for-the-python-rule-engine/ |
michael-conway
added a commit
that referenced
this issue
Oct 3, 2017
michael-conway
added a commit
that referenced
this issue
Oct 6, 2017
key iRODS code points irule.cpp /* add key val for specifying instance on which to run rule */
if ( argsMap.count( "rule-engine-plugin-instance" ) ) {
addKeyVal( &execMyRuleInp.condInput, irods::CFG_INSTANCE_NAME_KW.c_str(), argsMap["rule-engine-plugin-instance"].as<std::string>().c_str() );
} const std::string CFG_INSTANCE_NAME_KW("instance_name"); |
michael-conway
added a commit
that referenced
this issue
Oct 12, 2017
michael-conway
added a commit
that referenced
this issue
Oct 21, 2017
michael-conway
added a commit
that referenced
this issue
Oct 21, 2017
michael-conway
added a commit
that referenced
this issue
Oct 22, 2017
michael-conway
added a commit
that referenced
this issue
Oct 25, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
per RE: [iROD-Chat:16899] rule engine weirdness when Python engaged
Add a rule engine instance flag to the exec rule code
You need to specify the rule engine instance which handles the irule invocation. Since python is first it will try to service the native rule language irule request, assuming you did not specify the native rule engine instance which I presume is second in the json array.
https://docs.irods.org/4.2.1/icommands/user/#irule
--rule-engine-plugin-instance,-r - run rule on the specified rule engine instance
The text was updated successfully, but these errors were encountered: