Recent Changes

2021-11: version 42.3

• Enforce unix style line endings (\n) when writing files

2021-10: version 42.2

• Bug fix for 'clone' to support Python 2.7

• Ability to use different app.config file per command using '-c' flag

2021-08: version 42.1

• No major changes. Just bumping build number to coincide with other builds

2021-08: version 42.0

• codegen now generates a template for App's to be developed to run in a Python >= 3.6 environment.

• Bug fixes.

• Support for collecting incident types in codegen and extract. See the command line parameters -i and --incidenttype.

2021-06: version 41.1

• To address a security vulnerability, the Dockerfile codegen template now assigns user 1001 to the non-root group 1001. User 1001 is used to run a container.

• Added a new Atomic Function template generated with codegen, which is a condensed version of our Original Function template. It includes comments on best practices.

2021-05: version 41.0

• List all setup.py "install_requires" dependencies in docgen README template

• Bug fixes

2021-03: version 40.2

• Bug fix for to use setuptools_scm < 6.0.0 for Python 2.7 environments

2021-03: version 40.1

• Adjust entrypoint.sh template to ensure resilient-circuits is restarted when a fatal error occurs when running on App Host

• Added timestamp to logs on App Host

IBM Resilient SDK

Table of Contents

• Overview
• Installation
• Usage
• Supported Python Versions
• Documentation
• License and Terms

Overview

The IBM Resilient SDK provides the tools and infrastructure you need to develop Resilient Apps, which you can then post on App Exchange.

Installation

To install the IBM Resilient SDK, simply execute the following command:

$ pip install resilient-sdk

Usage

codegen:

Generate boilerplate code to start developing an app.

$ resilient-sdk codegen -p <name_of_package> -m 'fn_custom_md' --rule 'Rule One' 'Rule Two'

Note: When using --incidenttype for a child custom incident type, refer instead to the parent incident type.

docgen:

Generate documentation for an app.

$ resilient-sdk docgen -p <path_to_package>

extract:

Extract data in order to publish a .res file.

$ resilient-sdk extract -m 'fn_custom_md' --rule 'Rule One' 'Rule Two'

package:

Package an integration into a Resilient app.

$ resilient-sdk package -p <path_to_directory> --display-name "My Custom app"

clone:

Duplicate an existing Action related object (Function, Rule, Script, Message Destination, Workflow) with a new api or display name

$ resilient-sdk clone --workflow <workflow_to_be_cloned> <new_workflow_name>

$ resilient-sdk clone --workflow <workflow_to_be_cloned> <new_workflow_name> --changetype artifact

Supported Python Versions

Python 2.7+ and Python 3.6+

Documentation

For details on the Resilient SDK commands, use the -h option on the command line. For example, resilient-sdk -h and resilient-sdk codegen -h.

The Resilient App Developer's Guide provides information on using the Resilient SDK to develop and package apps. The guide is available on the IBM Knowledge Center at ibm.biz/resilient-docs. On this web page, select your Resilient platform version. On the follow-on page, you can find the App Developer's Guide by expanding Resilient Apps in the Table of Contents pane.

License and Terms

Copyright © IBM Corporation 2020

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.