IBM Security Resilient

Expand all | Collapse all

Functions are now "funct_{function_name}.py" ?

  • 1.  Functions are now "funct_{function_name}.py" ?

    Posted Wed October 16, 2019 05:14 PM
    Edited by Jared Fagel Wed October 16, 2019 11:40 PM
    I upgraded the resilient and resilient-circuits packages today, and then later tried to build a custom function.

    At first, I was confused and thought I was at fault, but I went and looked at the source code, and it appears a change was made to how custom function (files) are named during codegen.

    I had also tried to force not having the "funct_" prepended by using the -o switch (as documented in the Function Developer Guide), but this did not work as designed (continued to prepend "funct_").

    I did not see this change documented anywhere, and I even reviewed the 34.0 KB.

    Is there anything different that needs to happen now with this change? Is there any information on this change otherwise?

    ------------------------------
    Jared Fagel
    Cyber Security Analyst Intern
    Public Utility
    ------------------------------


  • 2.  RE: Functions are now "funct_{function_name}.py" ?

    Posted Thu October 17, 2019 05:21 AM
    I have upgraded my circuits to latest version also (resilient-circuits-34.0.194) and noticed these changes.
    However, the process of creating and deploying custom python integration is the same (I mean sequence of commands+parameters for this), and I've met no errors when tried to make another one for testing purposes.

    Can you share some details of your issue?

    ------------------------------
    Maksym Matviienko
    ------------------------------



  • 3.  RE: Functions are now "funct_{function_name}.py" ?

    Posted Thu October 17, 2019 07:48 AM
    Hi Jared,

    The changes were made to avoid situations with virtual environments which occurred when the package name matched the module name. There is no dependency with the module name that you can't rename it if you wish. The newest logic in setup.py configures the entry points regardless of the module name.

    Cheers,
    Mark

    ------------------------------
    Mark Scherfling
    ------------------------------



  • 4.  RE: Functions are now "funct_{function_name}.py" ?

    Posted Thu October 17, 2019 10:52 AM
    Thanks for that information Mark!

    ------------------------------
    Jared Fagel
    Cyber Security Analyst Intern
    Public Utility
    ------------------------------