Retired adapters
Adapters are occasionally retired. When an adapter is retired, it is first deprecated and then, after approximately one year, archived.
Deprecation
When an adapter is deprecated, it is moved from the top level to a subgroup in GitLab called Deprecated. The project description and the description within the package.json will include the word “Deprecated.” The README will include a paragraph at the top stating when it was deprecated, when it will be archived, and the replacement adapter if one is available. The adapter’s metadata is also updated with the deprecation date and replacement information.
The adapter remains available but will no longer be supported or receive security updates, and it is removed from the Itential Automation Marketplace. Deprecation notices are included in the monthly Product Release Notes.
You may continue using deprecated adapters; however, because deprecated adapters no longer receive updates, they may eventually become incompatible with future versions of Itential Platform or Node. Itential recommends installing the latest adapter version available in the Itential Automation Marketplace alongside the deprecated adapter and gradually converting your workflows to use the new adapter.
Archive
When an adapter is archived, it is moved from the Deprecated folder to a private Archive. The adapter project is made private and archived in GitLab so that it no longer appears in any searches. The adapter is no longer available and will not receive further updates or maintenance.
You may continue using archived adapters; however, because archived adapters no longer receive updates, they may eventually become incompatible with future versions of Itential Platform or Node. Itential recommends installing the latest adapter version available in the Itential Automation Marketplace alongside the archived adapter and converting your workflows to use the new adapter before the old adapter becomes incompatible.
