Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Overview

The purpose of this page is to provide a landing place for information on taking an existing ThreatConnect integration up to TcEx 2.0. This document is intended for review by the technical audience responsible for developing and maintaining code.

This page applies specifically to in-platform and external Python-based integrations that make use of the TcEx Framework. This page does not apply to integrations using the REST API or any other framework.

Changes in TcEx 2.0

Most importantly, we recommend reviewing the release notes for TcEx 2.0+. You can find the notes starting with the initial release of TcEx 2.0 here.

Specifically, some items of note that have changed are below:

  1. The tcex.request module has been removed. Integrations should make use of the tcex.session_external property to make remote calls from within the Platform. This property returns a requests object properly configured for the in-Platform environment.

  2. The datetime utilities offered in TcEx have been moved to tcex.utils.datetime now. See this page for more information.

  3. Several changes have been made to the available app decorators to improve usability. See this page for more information.

More recently-developed integrations making use of TcEx v1.1.6 or newer are likely to find the changes subtle and easy-adapted into the existing project. If you require assistance with your changes, please reach out to the Technology Partners team.

Updated Project Templates

If you’ve already initiated a project using the TcEx 1.x framework, you may wish to reinitialize your project using the update templates that go along with TcEx 2.0. These have been updated with changes to reflect some new uses with the Platform.

  • No labels