Retired Adapters

Retired Adapters

It is not very often that we retire adapters, however from time to time this will happen for one reason or another. When an adapter is retired, it will first be deprecated and then after about a year, it will be archived.

Deprecation

When an Adapter is deprecated, it will be moved from the top level to a sub group in GitLab called Deprecated. The project description and description within the package.json will include the word Deprecated. The README will include a paragraph at the top that states when it was deprecated, when it will be archived and the replacement if one is available. Finally, the metadata for the Adapter will also be updated with date and replacement information.

The Adapter will still be available, but will no longer be supported or receive security updates. The Adapter will be removed from the Itential Autoamtion Marketplace. Notification of the deprecation will be sent out in the monthly Product Release Notes.

Customers may continue using adapters once deprecated, however, since deprecated adapters are no longer receiving updates, they may eventually become incompatible with future versions of IAP or Node. Itential recommends using the latest adapter version available in the Itential Automation Marketplace in parallel with the deprecated adapter and over time converting your workflows to use the new adapter.

Archive

When an Adapter is archived, it will be moved from the Deprecated folder to an Archive (which is private). The adapter project will be made private and archived in GitLab so that it no longer appears in any searches. The Adapter will no longer be available and will no longer be updated or maintained!

Customers may continue using adapters once archived, however, since archived adapters are no longer receiving updates, they may eventually become incompatible with future versions of IAP or Node. Itential recommends using the latest adapter version available in the Itential marketplace in parallel with the deprecated adapter and converting your workflows to use the new adapter before the old adapter is incompatible.