@itentialopensource/adapter-db_mssql 1.0.6 → 1.1.0

package/.eslintrc.js

@@ -9,6 +9,7 @@ module.exports = {
     'json'
   ],
   parserOptions: {
+    ecmaVersion: 2020,
     sourceType: 'module'
   },
   rules: {

package/AUTH.md

@@ -1,13 +1,15 @@
 ## Authenticating Microsoft SQL Adapter 
 
-This document will go through the steps for authenticating the Microsoft SQL adapter with. Properly configuring the properties for an adapter in IAP is critical for getting the adapter online. You can read more about adapter authentication <a href="https://docs.itential.com/opensource/docs/authentication" target="_blank">HERE</a>. 
+This document will go through the steps for authenticating the Microsoft SQL adapter with. Properly configuring the properties for an adapter in Itential Platform is critical for getting the adapter online. You can read more about adapter authentication <a href="https://docs.itential.com/opensource/docs/authentication" target="_blank">HERE</a>. 
+
+If Itential Platform is running in docker, and MicrosoftSQL server is running in the local machine, host in adapter properties should be 'host.docker.internal' instead of 'localhost' or '127.0.0.1'.
 
 ### Database Library Authentication
 The Microsoft SQL adapter requires Database Library Authentication. If you change authentication methods, you should change this section accordingly and merge it back into the adapter repository.
 
 STEPS  
 1. Ensure you have access to a Microsoft SQL server and that it is running
-2. Follow the steps in the README.md to import the adapter into IAP if you have not already done so
+2. Follow the steps in the README.md to import the adapter into Itential Platform if you have not already done so
 3. Use the properties below for the ```properties.authentication``` field
 ```json
 "authentication": {
@@ -21,6 +23,6 @@ STEPS
 
 ### Troubleshooting
 - Make sure you copied over the correct username and password.
-- Turn on debug level logs for the adapter in IAP Admin Essentials.
+- Turn on debug level logs for the adapter in Itential Platform Admin Essentials.
 - Investigate the logs
 - Credentials should be ** masked ** by the adapter so make sure you verify the username and password - including that there are erroneous spaces at the front or end.

package/CALLS.md

@@ -4,7 +4,7 @@ The `adapter.js` file contains the calls the adapter makes available to the rest
 
 ### Generic Adapter Calls
 
-These are adapter methods that IAP or you might use. There are some other methods not shown here that might be used for internal adapter functionality.
+These are adapter methods that Itential Platform or you might use. There are some other methods not shown here that might be used for internal adapter functionality.
 
 <table border="1" class="bordered-table">
   <tr>

package/ENHANCE.md

@@ -2,11 +2,11 @@
 
 ### Adding a Second Instance of an Adapter
 
-You can add a second instance of this adapter without adding new code on the file system. To do this go into the IAP Admin Essentials and add a new service config for this adapter. The two instances of the adapter should have unique ids. In addition, they should point to different instances (unique host and port) of the other system.
+You can add a second instance of this adapter without adding new code on the file system. To do this go into the Itential Platform Admin Essentials and add a new service config for this adapter. The two instances of the adapter should have unique ids. In addition, they should point to different instances (unique host and port) of the other system.
 
 ### Adding Adapter Properties
 
-While changing adapter properties is done in the service instance configuration section of IAP, adding properties has to be done in the adapter. To add a property you should edit the propertiesSchema.json with the proper information for the property. In addition, you should modify the sampleProperties to have the new property in it.
+While changing adapter properties is done in the service instance configuration section of Itential Platform, adding properties has to be done in the adapter. To add a property you should edit the propertiesSchema.json with the proper information for the property. In addition, you should modify the sampleProperties to have the new property in it.
 
 ```text
 Files to update

package/PROPERTIES.md

@@ -1,6 +1,6 @@
 ## Configuration
 
-This section defines **all** the properties that are available for the adapter, including detailed information on what each property is for. If you are not using certain capabilities with this adapter, you do not need to define all of the properties. An example of how the properties for this adapter can be used with tests or IAP are provided in the sampleProperties.
+This section defines **all** the properties that are available for the adapter, including detailed information on what each property is for. If you are not using certain capabilities with this adapter, you do not need to define all of the properties. An example of how the properties for this adapter can be used with tests or Itential Platform are provided in the sampleProperties.
 
 ```json
   {
@@ -54,7 +54,7 @@ These base properties are used to connect to MicrosoftSQL upon the adapter initi
 </table>
 <br>
 
-A connectivity check tells IAP the adapter has loaded successfully.
+A connectivity check tells Itential Platform the adapter has loaded successfully.
 
 ### Authentication Properties
 

package/README.md

@@ -1,20 +1,296 @@
-MicrosoftSQL Adapter
-===========
+# Adapter for MicrosoftSQL 
 
-This adapter allows interaction with a MicrosoftSQL server. For efficiency, this adapter should only be used in IAP workflow calls. Calling the adapter from Applications instead of using the npm mssql pacakge will be less efficient!
+## Table of Contents
 
-Notes:
-1. If IAP is running in docker, and MicrosoftSQL server is running in the local machine, host in adapter properties should be 'host.docker.internal' instead of 'localhost' or '127.0.0.1'.
+Some of the page links in this document and links to other GitLab files do not work in Confluence however, the information is available in other sections of the Confluence material.
 
-License & Maintainers
----
+- [Specific to this Adapter](#specific-to-this-adapter)
+  - [Authentication](./AUTH.md)
+  - [Sample Properties](./sampleProperties.json)
+  - [Available Calls](./CALLS.md)
+  - [Swagger](./report/adapter-openapi.json)
+- [Generic Adapter Information](#generic-adapter-information)
+  - [Overview](./SUMMARY.md)
+  - [Versioning](#versioning)
+  - [Supported Platform Versions](#supported-platform-versions)
+  - [Getting Started](#getting-started)
+    - [Helpful Background Information](#helpful-background-information)
+    - [Prerequisites](#prerequisites)
+    - [How to Install](#how-to-install)
+    - [Testing](#testing)
+  - [Configuration](./PROPERTIES.md)
+  - [Utilities](./UTILITIES.md)
+  - [Additional Information](#additional-information)
+    - [Enhancements](./ENHANCE.md)
+    - [Contributing](./CONTRIBUTING.md)
+    - [Helpful Links](#helpful-links)
+    - [Node Scripts](#node-scripts)
+  - [Troubleshoot](./TROUBLESHOOT.md)
+  - [License and Maintainers](#license-and-maintainers)
+  - [Product License](#product-license)
 
-### Maintained by:
 
-Itential Adapter Team (<product_team@itential.com>)
+## Specific to this Adapter
 
-Check the [changelog](CHANGELOG.md) for the latest changes.
+### [Authentication](./AUTH.md)
 
-### License
+### [Sample Properties](./sampleProperties.json)
 
-Itential, LLC proprietary
+<a href="./sampleProperties.json" target="_blank">Sample Properties</a> can be used to help you configure the adapter in the Itential Automation Platform. You will need to update connectivity information such as the host, port, protocol and credentials.
+
+### [Available Calls](./CALLS.md)
+
+### [Swagger](./report/adapter-openapi.json)
+
+
+## Generic Adapter Information
+
+### [Overview](./SUMMARY.md)
+
+### Versioning
+
+Itential Product and opensource adapters utilize SemVer for versioning. The current version of the adapter can be found in the `package.json` file or viewed in the Platform GUI on the System page. All Itential opensource adapters can be found in the <a href="https://gitlab.com/itentialopensource/adapters" target="_blank">Itential OpenSource Repository</a>.
+
+Any release prior to 1.0.0 is a pre-release. Initial builds of adapters are generally set up as pre-releases as there is often work that needs to be done to configure the adapter and make sure the authentication process to MicrosoftSQL works appropriately.
+
+Release notes can be viewed in CHANGELOG.md.
+
+### Supported Platform Versions
+
+Itential Product adapters are built for particular versions of Platform and packaged with the versions they work with. 
+
+Itential opensource adapter as well as custom adapters built with the Itential Adapter Builder work acoss many releases of Platform. As a result, it is not often necessary to modify an adapter when upgrading Platform. If Platform has changes that impact the pronghorn.json, like adding a new required section, this will most likely require changes to all adapters when upgrading Platform.
+
+Many of the scripts that come with all adapters built using the Itential Adapter Builder do have some dependencies on Platform or the Platform database schema and so it is possible these scripts could stop working in different versions of Platform. If you notify Itential of any issues, the Adapter Team will attempt to fix the scripts for newer releases of Platform.
+
+### Getting Started
+
+These instructions will help you get a copy of the project on your local machine for development and testing. Reading this section is also helpful for deployments as it provides you with pertinent information on prerequisites and properties.
+
+#### Helpful Background Information
+
+There is <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter documentation available on the Itential Documentation Site</a>. This documentation includes information and examples that are helpful for:
+
+```text
+Authentication
+Platform Service Instance Configuration
+Code Files
+Endpoint Configuration (Action & Schema)
+Mock Data
+Adapter Generic Methods
+Headers
+Security
+Linting and Testing
+Build an Adapter
+Troubleshooting an Adapter
+```
+
+Others will be added over time.
+Want to build a new adapter? Use the <a href="https://adapters.itential.io" target="_blank">Itential Adapter Builder</a>
+
+#### Prerequisites
+
+The following is a list of required packages for installation on the system the adapter will run on:
+
+```text
+Node.js
+npm
+Git
+```
+
+The following list of packages are required for Itential opensource adapters or custom adapters that have been built utilizing the Itential Adapter Builder. You can install these packages by running npm install inside the adapter directory.
+
+<table border="1" class="bordered-table">
+  <tr>
+    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Package</span></th>
+    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
+  </tr>
+  <tr>
+    <td style="padding:15px">@itentialopensource/adapter-utils</td>
+    <td style="padding:15px">Runtime library classes for all adapters;  includes request handling, connection, authentication throttling, and translation.</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">ajv</td>
+    <td style="padding:15px">Required for validation of adapter properties to integrate with MicrosoftSQL.</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">axios</td>
+    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">commander</td>
+    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">fs-extra</td>
+    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">mocha</td>
+    <td style="padding:15px">Testing library that is utilized by some of the node scripts that are included with the adapter.</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">mocha-param</td>
+    <td style="padding:15px">Testing library that is utilized by some of the node scripts that are included with the adapter.</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">mongodb</td>
+    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">nyc</td>
+    <td style="padding:15px">Testing coverage library that is utilized by some of the node scripts that are included with the adapter.</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">ping</td>
+    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">readline-sync</td>
+    <td style="padding:15px">Utilized by the node script that comes with the adapter;  helps to test unit and integration functionality.</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">semver</td>
+    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">winston</td>
+    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
+  </tr>
+</table>
+<br>
+
+If you are developing and testing a custom adapter, or have testing capabilities on an Itential opensource adapter, you will need to install these packages as well.
+
+```text
+chai
+eslint
+eslint-config-airbnb-base
+eslint-plugin-import
+eslint-plugin-json
+testdouble
+```
+
+#### How to Install
+
+1a. If you are working on Itential Platform 2023.2 or earlier versions, set up the name space location in your Itential Platform node_modules.
+
+```bash
+cd /opt/pronghorn/current/node_modules (* could be in a different place)
+if the @itentialopensource directory does not exist, create it:
+    mkdir @itentialopensource
+cd @itentialopensource
+```
+
+1b. If you are working on Platform 6, you need to install the adapter in the services directory.
+
+```bash
+cd /opt/itential/platform/services (* you may have configured it to be in a different place)
+```
+
+2. Clone/unzip/tar the adapter into your Platform environment.
+
+```bash
+git clone git@gitlab.com:@itentialopensource/adapters/adapter-db_mssql
+or
+unzip adapter-db_mssql.zip
+or
+tar -xvf adapter-db_mssql.tar
+```
+
+3. install the adapter dependencies.
+
+```bash
+cd adapter-db_mssql
+npm install
+npm run lint:errors
+npm run test
+```
+
+4. Restart Platform
+
+```bash
+systemctl restart pronghorn
+```
+
+5. Create an adapter service instance configuration in Platform Admin Essentials GUI
+
+6. Copy the properties from the sampleProperties.json and paste them into the service instance configuration in the inner/second properties field.
+
+7. Change the adapter service instance configuration (host, port, credentials, etc) in Platform Admin Essentials GUI
+
+#### Testing
+
+Mocha is generally used to test all Itential Opensource Adapters. There are unit tests as well as integration tests performed. Integration tests can generally be run as standalone using mock data and running the adapter in stub mode, or as integrated. When running integrated, every effort is made to prevent environmental failures, however there is still a possibility.
+
+##### Unit Testing
+
+Unit Testing includes testing basic adapter functionality as well as error conditions that are triggered in the adapter prior to any integration. There are two ways to run unit tests. The prefered method is to use the testRunner script; however, both methods are provided here.
+
+```bash
+node utils/testRunner --unit
+
+npm run test:unit
+npm run test:baseunit
+```
+
+To add new unit tests, edit the `test/unit/adapterTestUnit.js` file. The tests that are already in this file should provide guidance for adding additional tests.
+
+##### Integration Testing - Standalone
+
+Standalone Integration Testing requires mock data to be provided with the entities. If this data is not provided, standalone integration testing will fail. When the adapter is set to run in stub mode (setting the stub property to true), the adapter will run through its code up to the point of making the request. It will then retrieve the mock data and return that as if it had received that data as the response from MicrosoftSQL. It will then translate the data so that the adapter can return the expected response to the rest of the Itential software. Standalone is the default integration test.
+
+Similar to unit testing, there are two ways to run integration tests. Using the testRunner script is better because it prevents you from having to edit the test script; it will also resets information after testing is complete so that credentials are not saved in the file.
+
+```bash
+node utils/testRunner
+  answer no at the first prompt
+
+npm run test:integration
+```
+
+To add new integration tests, edit the `test/integration/adapterTestIntegration.js` file. The tests that are already in this file should provide guidance for adding additional tests.
+
+##### Integration Testing
+
+Integration Testing requires connectivity to MicrosoftSQL. By using the testRunner script it prevents you from having to edit the integration test. It also resets the integration test after the test is complete so that credentials are not saved in the file.
+
+> **Note**: These tests have been written as a best effort to make them work in most environments. However, the Adapter Builder often does not have the necessary information that is required to set up valid integration tests. For example, the order of the requests can be very important and data is often required for `creates` and `updates`. Hence, integration tests may have to be enhanced before they will work (integrate) with MicrosoftSQL. Even after tests have been set up properly, it is possible there are environmental constraints that could result in test failures. Some examples of possible environmental issues are customizations that have been made within MicrosoftSQL which change order dependencies or required data.
+
+```bash
+node utils/testRunner
+answer yes at the first prompt
+answer all other questions on connectivity and credentials
+```
+
+Test should also be written to clean up after themselves. However, it is important to understand that in some cases this may not be possible. In addition, whenever exceptions occur, test execution may be stopped, which will prevent cleanup actions from running. It is recommended that tests be utilized in dev and test labs only.
+
+> **Reminder**: Do not check in code with actual credentials to systems.
+
+### [Configuration](./PROPERTIES.md)
+
+### [Utilities](./UTILITIES.md)
+
+### Additional Information
+
+#### [Enhancements](./ENHANCE.md)
+
+#### [Contributing](./CONTRIBUTING.md)
+
+#### Helpful Links
+
+<a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter Technical Resources</a>
+
+### [Troubleshoot](./TROUBLESHOOT.md)
+
+### License and Maintainers
+
+```text
+Itential Product Adapters are maintained by the Itential Product Team.
+Itential OpenSource Adapters are maintained by the Itential Adapter Team and the community at large.
+Custom Adapters are maintained by other sources.
+```
+
+### Product License
+
+[Apache 2.0](./LICENSE)

package/SUMMARY.md

@@ -1,9 +1,9 @@
 ## Overview
 
-This adapter is used to integrate the Itential Automation Platform (IAP) with the MicrosoftSQL System. The API that was used to build the adapter for MicrosoftSQL is usually available in the report directory of this adapter. The adapter utilizes the MicrosoftSQL API to provide the integrations that are deemed pertinent to IAP. The ReadMe file is intended to provide information on this adapter it is generated from various other Markdown files.
+This adapter is used to integrate the Itential Platform  with the MicrosoftSQL System. The API that was used to build the adapter for MicrosoftSQL is usually available in the report directory of this adapter. The adapter utilizes the MicrosoftSQL API to provide the integrations that are deemed pertinent to Itential Platform . The ReadMe file is intended to provide information on this adapter it is generated from various other Markdown files.
 
 >**Note**: It is possible that some integrations will be supported through the MicrosoftSQL adapter while other integrations will not. If you need additional API calls, you can use the Update capabilities provided by the Adapter Builder or request Itential to add them if the Adapter is an Itential opensourced adapter.
 
 Itential provides information on all of its product adapters in the Customer Knowledge Base. Information in the <a href="https://itential.atlassian.net/servicedesk/customer/portals" target="_blank">Customer Knowledge Base</a> is consistently maintained and goes through documentation reviews. As a result, it should be the first place to go for information.
 
-For opensourced and custom built adapters, the ReadMe is a starting point to understand what you have built, provide the information for you to be able to update the adapter, and assist you with deploying the adapter into IAP.
+For opensourced and custom built adapters, the ReadMe is a starting point to understand what you have built, provide the information for you to be able to update the adapter, and assist you with deploying the adapter into Itential Platform .

package/SYSTEMINFO.md

@@ -14,7 +14,7 @@ We classify MSSQL into the Data Storage domaina as MSSQL is a database which pro
 "Industry-leading performance and availability"
 
 ## Why Integrate
-The MSSQL adapter from Itential is used to integrate the Itential Automation Platform (IAP) with Microsoft MSSQL. With this adapter you have the ability to perform operations with MSSQL on items such as:
+The MSSQL adapter from Itential is used to integrate the Itential Platform with Microsoft MSSQL. With this adapter you have the ability to perform operations with MSSQL on items such as:
 
 - Storage of Information
 - Retrieval of Information

package/TAB1.md

@@ -1,9 +1,9 @@
 # Overview 
 
-This adapter is used to integrate the Itential Automation Platform (IAP) with the MicrosoftSQL System. The API that was used to build the adapter for MicrosoftSQL is usually available in the report directory of this adapter. The adapter utilizes the MicrosoftSQL API to provide the integrations that are deemed pertinent to IAP. The ReadMe file is intended to provide information on this adapter it is generated from various other Markdown files.
+This adapter is used to integrate the Itential Platform  with the MicrosoftSQL System. The API that was used to build the adapter for MicrosoftSQL is usually available in the report directory of this adapter. The adapter utilizes the MicrosoftSQL API to provide the integrations that are deemed pertinent to Itential Platform . The ReadMe file is intended to provide information on this adapter it is generated from various other Markdown files.
 
 ## Details 
-The MSSQL adapter from Itential is used to integrate the Itential Automation Platform (IAP) with Microsoft MSSQL. With this adapter you have the ability to perform operations with MSSQL on items such as:
+The MSSQL adapter from Itential is used to integrate the Itential Platform with Microsoft MSSQL. With this adapter you have the ability to perform operations with MSSQL on items such as:
 
 - Storage of Information
 - Retrieval of Information

package/TAB2.md

@@ -11,14 +11,16 @@
 ## Specific Adapter Information
 ### Authentication
 
-This document will go through the steps for authenticating the Microsoft SQL adapter with. Properly configuring the properties for an adapter in IAP is critical for getting the adapter online. You can read more about adapter authentication <a href="https://docs.itential.com/opensource/docs/authentication" target="_blank">HERE</a>. 
+This document will go through the steps for authenticating the Microsoft SQL adapter with. Properly configuring the properties for an adapter in Itential Platform is critical for getting the adapter online. You can read more about adapter authentication <a href="https://docs.itential.com/opensource/docs/authentication" target="_blank">HERE</a>. 
+
+If Itential Platform is running in docker, and MicrosoftSQL server is running in the local machine, host in adapter properties should be 'host.docker.internal' instead of 'localhost' or '127.0.0.1'.
 
 #### Database Library Authentication
 The Microsoft SQL adapter requires Database Library Authentication. If you change authentication methods, you should change this section accordingly and merge it back into the adapter repository.
 
 STEPS  
 1. Ensure you have access to a Microsoft SQL server and that it is running
-2. Follow the steps in the README.md to import the adapter into IAP if you have not already done so
+2. Follow the steps in the README.md to import the adapter into Itential Platform if you have not already done so
 3. Use the properties below for the ```properties.authentication``` field
 ```json
 "authentication": {
@@ -32,12 +34,12 @@ STEPS
 
 #### Troubleshooting
 - Make sure you copied over the correct username and password.
-- Turn on debug level logs for the adapter in IAP Admin Essentials.
+- Turn on debug level logs for the adapter in Itential Platform Admin Essentials.
 - Investigate the logs
 - Credentials should be ** masked ** by the adapter so make sure you verify the username and password - including that there are erroneous spaces at the front or end.
 ### Sample Properties
 
-Sample Properties can be used to help you configure the adapter in the Itential Automation Platform. You will need to update connectivity information such as the host, port, protocol and credentials.
+Sample Properties can be used to help you configure the adapter in the Itential Platform. You will need to update connectivity information such as the host, port, protocol and credentials.
 
 ```json
   "properties": {

package/package.json

@@ -1,13 +1,12 @@
 {
   "name": "@itentialopensource/adapter-db_mssql",
-  "version": "1.0.6",
+  "version": "1.1.0",
   "description": "Itential adapter to connect to mssql",
   "main": "adapter.js",
   "wizardVersion": "2.44.7",
-  "engineVersion": "1.67.14",
+  "engineVersion": "1.69.14",
   "adapterType": "library",
   "scripts": {
-    "artifactize": "npm i && node utils/packModificationScript.js",
     "preinstall": "node utils/setup.js",
     "deinstall": "node utils/removeHooks.js",
     "lint": "node --max_old_space_size=4096 ./node_modules/eslint/bin/eslint.js . --ext .json --ext .js",
@@ -20,10 +19,9 @@
   },
   "keywords": [
     "Itential",
-    "IAP",
+    "Itential Platform",
     "Automation",
     "Integration",
-    "App-Artifacts",
     "Adapter",
     "Persistence",
     "MicrosoftSQL",
@@ -41,20 +39,20 @@
   "author": "Itential",
   "homepage": "https://gitlab.com/itentialopensource/adapters/adapter-db_mssql#readme",
   "dependencies": {
-    "ajv": "^8.17.1",
-    "fs-extra": "^11.2.0",
-    "mssql": "^10.0.1",
-    "readline-sync": "^1.4.10"
+    "ajv": "8.17.1",
+    "fs-extra": "11.3.0",
+    "mssql": "10.0.1",
+    "readline-sync": "1.4.10",
+    "mocha": "10.8.2",
+    "winston": "3.17.0"
   },
   "devDependencies": {
-    "chai": "^4.3.7",
-    "eslint": "^8.44.0",
-    "eslint-config-airbnb-base": "^15.0.0",
-    "eslint-plugin-import": "^2.27.5",
-    "eslint-plugin-json": "^3.1.0",
-    "mocha": "^10.7.0",
-    "testdouble": "^3.18.0",
-    "winston": "^3.13.1"
+    "chai": "4.5.0",
+    "eslint": "8.57.0",
+    "eslint-config-airbnb-base": "15.0.0",
+    "eslint-plugin-import": "2.31.0",
+    "eslint-plugin-json": "3.1.0",
+    "testdouble": "3.18.0"
   },
   "private": false
 }

package/test/integration/adapterTestIntegration.js

@@ -13,9 +13,9 @@ const path = require('path');
 const winston = require('winston');
 const { expect } = require('chai');
 const { use } = require('chai');
+const log = require('../../utils/logger');
 
 // stub and attemptTimeout are used throughout the code so set them here
-let logLevel = 'none';
 const stub = true;
 const isRapidFail = false;
 const isSaveMockData = false;
@@ -64,43 +64,6 @@ global.pronghornProps = {
 
 global.$HOME = `${__dirname}/../..`;
 
-// set the log levels that Pronghorn uses, spam and trace are not defaulted in so without
-// this you may error on log.trace calls.
-const myCustomLevels = {
-  levels: {
-    spam: 6,
-    trace: 5,
-    debug: 4,
-    info: 3,
-    warn: 2,
-    error: 1,
-    none: 0
-  }
-};
-
-// need to see if there is a log level passed in
-process.argv.forEach((val) => {
-  // is there a log level defined to be passed in?
-  if (val.indexOf('--LOG') === 0) {
-    // get the desired log level
-    const inputVal = val.split('=')[1];
-
-    // validate the log level is supported, if so set it
-    if (Object.hasOwnProperty.call(myCustomLevels.levels, inputVal)) {
-      logLevel = inputVal;
-    }
-  }
-});
-
-// need to set global logging
-global.log = winston.createLogger({
-  level: logLevel,
-  levels: myCustomLevels.levels,
-  transports: [
-    new winston.transports.Console()
-  ]
-});
-
 /**
  * Runs the common asserts for test
  */

package/test/unit/adapterTestUnit.js

@@ -17,12 +17,12 @@ const { expect } = require('chai');
 const { use } = require('chai');
 const td = require('testdouble');
 const Ajv = require('ajv');
+const log = require('../../utils/logger');
 
 const ajv = new Ajv({ strictSchema: false, allErrors: true, allowUnionTypes: true });
 const anything = td.matchers.anything();
 
 // stub and attemptTimeout are used throughout the code so set them here
-let logLevel = 'none';
 const stub = true;
 const isRapidFail = false;
 const attemptTimeout = 120000;
@@ -70,43 +70,6 @@ global.pronghornProps = {
 
 global.$HOME = `${__dirname}/../..`;
 
-// set the log levels that Pronghorn uses, spam and trace are not defaulted in so without
-// this you may error on log.trace calls.
-const myCustomLevels = {
-  levels: {
-    spam: 6,
-    trace: 5,
-    debug: 4,
-    info: 3,
-    warn: 2,
-    error: 1,
-    none: 0
-  }
-};
-
-// need to see if there is a log level passed in
-process.argv.forEach((val) => {
-  // is there a log level defined to be passed in?
-  if (val.indexOf('--LOG') === 0) {
-    // get the desired log level
-    const inputVal = val.split('=')[1];
-
-    // validate the log level is supported, if so set it
-    if (Object.hasOwnProperty.call(myCustomLevels.levels, inputVal)) {
-      logLevel = inputVal;
-    }
-  }
-});
-
-// need to set global logging
-global.log = winston.createLogger({
-  level: logLevel,
-  levels: myCustomLevels.levels,
-  transports: [
-    new winston.transports.Console()
-  ]
-});
-
 /**
  * Runs the error asserts for the test
  */

package/utils/adapterInfo.js

@@ -1,20 +1,94 @@
 #!/usr/bin/env node
-/* @copyright Itential, LLC 2019 */
+/* @copyright Itential, LLC 2025 */
+
 /* eslint global-require:warn */
 /* eslint import/no-dynamic-require:warn */
 /* eslint prefer-destructuring:warn */
 
+/**
+ * This script will determine the information about the adapter and store
+ * it into a file in the adapter. This is self contained and only depends on
+ * finding files within the adapter to gather information.
+ *
+ * This utility is used when adapters are committed and pushed. It is not used by
+ * any customers nor is it references in any scripts.
+ */
+
 const path = require('path');
 const fs = require('fs-extra');
 
 /**
- * This script will determine the information about the adapter and store
- * it into a file in the adapter.
+ * @summary Count the number of lines in a file
+ * @param {string} filePath - The path to the file
+ * @returns {number} The total number of lines in the file
+ */
+function countLinesInFile(filePath) {
+  if (fs.existsSync(filePath)) {
+    const cFile = fs.readFileSync(filePath, 'utf8');
+    return cFile.split('\n').length;
+  }
+  console.log(`Missing - ${path.basename(filePath)}`);
+  return 0;
+}
+
+/**
+ * @summary Count the number of lines across multiple files
+ * @param {array} filePaths - An array of file paths
+ * @returns {number} The total number of lines across all files
+ */
+function countLinesInFiles(filePaths) {
+  return filePaths.reduce((total, filePath) => total + countLinesInFile(filePath), 0);
+}
+
+/**
+ * @summary Count the number of lines in all json files within an entity directory
+ * @param {string} entityDir - The entity directory
+ * @returns {number} The total number of lines across all JSON files in the entity directory
+ */
+function countEntityLines(entityDir) {
+  let totalLines = 0;
+
+  if (!fs.existsSync(entityDir)) {
+    console.log('Could not find the entities directory');
+    return totalLines;
+  }
+  const entities = fs.readdirSync(entityDir);
+  for (let e = 0; e < entities.length; e += 1) {
+    const entityPath = path.join(entityDir, entities[e]);
+    if (fs.statSync(entityPath).isDirectory()) {
+      const jsonFiles = fs.readdirSync(entityPath).filter((f) => f.endsWith('.json'));
+      for (let j = 0; j < jsonFiles.length; j += 1) {
+        totalLines += countLinesInFile(path.join(entityPath, jsonFiles[j]));
+      }
+    }
+  }
+  return totalLines;
+}
+
+/**
+ * @summary Count the number of test cases in a file
+ * @param {string} filePath - The path to the test file
+ * @returns {number} The total number of test cases in the file
  */
+function countTestsInFile(filePath) {
+  if (fs.existsSync(filePath)) {
+    const tFile = fs.readFileSync(filePath, 'utf8');
+    const ttestCount = tFile.split('it(\'').length;
+    return ttestCount;
+  }
+  console.log(`Missing - ${path.basename(filePath)}`);
+  return 0;
+}
 
 /**
- * get adapter information
+ * @summary Count the number of test cases across multiple files
+ * @param {array} filePaths - An array of test file paths
+ * @returns {number} The total number of test cases across all files
  */
+function countTestsInFiles(filePaths) {
+  return filePaths.reduce((total, filePath) => total + countTestsInFile(filePath), 0);
+}
+
 function adapterInfo() {
   // set the base pase of the adapter - tool shoud be one level up in utils
   let adaptdir = __dirname;
@@ -23,172 +97,43 @@ function adapterInfo() {
   if (adaptdir.endsWith('/utils')) {
     adaptdir = adaptdir.substring(0, adaptdir.length - 6);
   }
+
+  // if no package.json then not in right place - end with error
+  if (!fs.existsSync(`${adaptdir}/package.json`)) {
+    throw new Error('Missing - package.json');
+  }
   const pack = require(`${adaptdir}/package.json`);
   infoRes.version = pack.version;
 
   let configCount = 0;
-  if (fs.existsSync(`${adaptdir}/pronghorn.json`)) {
-    const cFile = fs.readFileSync(`${adaptdir}/pronghorn.json`, 'utf8');
-    configCount += cFile.split('\n').length;
-  } else {
-    console.log('Missing - pronghorn.json');
-  }
-  if (fs.existsSync(`${adaptdir}/propertiesSchema.json`)) {
-    const cFile = fs.readFileSync(`${adaptdir}/propertiesSchema.json`, 'utf8');
-    configCount += cFile.split('\n').length;
-  } else {
-    console.log('Missing - propertiesSchema.json');
-  }
-  if (fs.existsSync(`${adaptdir}/error.json`)) {
-    const cFile = fs.readFileSync(`${adaptdir}/error.json`, 'utf8');
-    configCount += cFile.split('\n').length;
-  } else {
-    console.log('Missing - error.json');
-  }
-  const entitydir = path.join(adaptdir, '/entities');
-  if (fs.existsSync(entitydir) && fs.statSync(entitydir).isDirectory()) {
-    const entities = fs.readdirSync(entitydir);
-    // need to go through each entity in the entities directory
-    for (let e = 0; e < entities.length; e += 1) {
-      if (fs.statSync(`${entitydir}/${entities[e]}`).isDirectory()) {
-        const cfiles = fs.readdirSync(entitydir);
-        for (let c = 0; c < cfiles.length; c += 1) {
-          if (cfiles[c].endsWith('.json')) {
-            const ccFile = fs.readFileSync(`${entitydir}/${entities[e]}/${cfiles[c]}`, 'utf8');
-            configCount += ccFile.split('\n').length;
-          }
-        }
-      }
-    }
-  } else {
-    console.log('Could not find the entities directory');
-  }
+  const configFiles = ['pronghorn.json', 'propertiesSchema.json', 'error.json'].map((f) => path.join(adaptdir, f));
+  configCount = countLinesInFiles(configFiles);
+
+  const entityDir = path.join(adaptdir, '/entities');
+  configCount += countEntityLines(entityDir);
+
   infoRes.configLines = configCount;
 
-  let scodeCount = 0;
-  if (fs.existsSync(`${adaptdir}/utils/artifactize.js`)) {
-    const sFile = fs.readFileSync(`${adaptdir}/utils/artifactize.js`, 'utf8');
-    scodeCount += sFile.split('\n').length;
-  } else {
-    console.log('Missing - utils/artifactize.js');
-  }
-  if (fs.existsSync(`${adaptdir}/utils/basicGet.js`)) {
-    const sFile = fs.readFileSync(`${adaptdir}/utils/basicGet.js`, 'utf8');
-    scodeCount += sFile.split('\n').length;
-  } else {
-    console.log('Missing - utils/basicGet.js');
-  }
-  if (fs.existsSync(`${adaptdir}/utils/checkMigrate.js`)) {
-    const sFile = fs.readFileSync(`${adaptdir}/utils/checkMigrate.js`, 'utf8');
-    scodeCount += sFile.split('\n').length;
-  } else {
-    console.log('Missing - utils/checkMigrate.js');
-  }
-  if (fs.existsSync(`${adaptdir}/utils/findPath.js`)) {
-    const sFile = fs.readFileSync(`${adaptdir}/utils/findPath.js`, 'utf8');
-    scodeCount += sFile.split('\n').length;
-  } else {
-    console.log('Missing - utils/findPath.js');
-  }
-  if (fs.existsSync(`${adaptdir}/utils/modify.js`)) {
-    const sFile = fs.readFileSync(`${adaptdir}/utils/modify.js`, 'utf8');
-    scodeCount += sFile.split('\n').length;
-  } else {
-    console.log('Missing - utils/modify.js');
-  }
-  if (fs.existsSync(`${adaptdir}/utils/packModificationScript.js`)) {
-    const sFile = fs.readFileSync(`${adaptdir}/utils/packModificationScript.js`, 'utf8');
-    scodeCount += sFile.split('\n').length;
-  } else {
-    console.log('Missing - utils/packModificationScript.js');
-  }
-  if (fs.existsSync(`${adaptdir}/utils/setup.js`)) {
-    const sFile = fs.readFileSync(`${adaptdir}/utils/setup.js`, 'utf8');
-    scodeCount += sFile.split('\n').length;
-  } else {
-    console.log('Missing - utils/setup.js');
-  }
-  if (fs.existsSync(`${adaptdir}/utils/tbScript.js`)) {
-    const sFile = fs.readFileSync(`${adaptdir}/utils/tbScript.js`, 'utf8');
-    scodeCount += sFile.split('\n').length;
-  } else {
-    console.log('Missing - utils/tbScript.js');
-  }
-  if (fs.existsSync(`${adaptdir}/utils/tbUtils.js`)) {
-    const sFile = fs.readFileSync(`${adaptdir}/utils/tbUtils.js`, 'utf8');
-    scodeCount += sFile.split('\n').length;
-  } else {
-    console.log('Missing - utils/tbUtils.js');
-  }
-  if (fs.existsSync(`${adaptdir}/utils/testRunner.js`)) {
-    const sFile = fs.readFileSync(`${adaptdir}/utils/testRunner.js`, 'utf8');
-    scodeCount += sFile.split('\n').length;
-  } else {
-    console.log('Missing - utils/testRunner.js');
-  }
-  if (fs.existsSync(`${adaptdir}/utils/troubleshootingAdapter.js`)) {
-    const sFile = fs.readFileSync(`${adaptdir}/utils/troubleshootingAdapter.js`, 'utf8');
-    scodeCount += sFile.split('\n').length;
-  } else {
-    console.log('Missing - utils/troubleshootingAdapter.js');
-  }
-  infoRes.scriptLines = scodeCount;
+  const utilFiles = ['argParser', 'checkMigrate.js', 'entitiesToDB.js', 'findPath.js', 'logger.js', 'methodDocumentor.js', 'modify.js', 'mongoDbConnection.js',
+    'mongoUtils.js', 'setup.js', 'taskMover.js', 'tbScript.js', 'tbUtils.js', 'testRunner.js', 'troubleshootingAdapter.js', 'updateAdapterConfig.js'
+  ].map((f) => path.join(adaptdir, 'utils', f));
 
-  let codeCount = 0;
-  if (fs.existsSync(`${adaptdir}/adapter.js`)) {
-    const aFile = fs.readFileSync(`${adaptdir}/adapter.js`, 'utf8');
-    codeCount += aFile.split('\n').length;
-  } else {
-    console.log('Missing - utils/adapter.js');
-  }
-  if (fs.existsSync(`${adaptdir}/adapterBase.js`)) {
-    const aFile = fs.readFileSync(`${adaptdir}/adapterBase.js`, 'utf8');
-    codeCount += aFile.split('\n').length;
-  } else {
-    console.log('Missing - utils/adapterBase.js');
-  }
-  infoRes.codeLines = codeCount;
-
-  let tcodeCount = 0;
-  let ttestCount = 0;
-  if (fs.existsSync(`${adaptdir}/test/integration/adapterTestBasicGet.js`)) {
-    const tFile = fs.readFileSync(`${adaptdir}/test/integration/adapterTestBasicGet.js`, 'utf8');
-    tcodeCount += tFile.split('\n').length;
-    ttestCount += tFile.split('it(\'').length;
-  } else {
-    console.log('Missing - test/integration/adapterTestBasicGet.js');
-  }
-  if (fs.existsSync(`${adaptdir}/test/integration/adapterTestConnectivity.js`)) {
-    const tFile = fs.readFileSync(`${adaptdir}/test/integration/adapterTestConnectivity.js`, 'utf8');
-    tcodeCount += tFile.split('\n').length;
-    ttestCount += tFile.split('it(\'').length;
-  } else {
-    console.log('Missing - test/integration/adapterTestConnectivity.js');
-  }
-  if (fs.existsSync(`${adaptdir}/test/integration/adapterTestIntegration.js`)) {
-    const tFile = fs.readFileSync(`${adaptdir}/test/integration/adapterTestIntegration.js`, 'utf8');
-    tcodeCount += tFile.split('\n').length;
-    ttestCount += tFile.split('it(\'').length;
-  } else {
-    console.log('Missing - test/integration/adapterTestIntegration.js');
-  }
-  if (fs.existsSync(`${adaptdir}/test/unit/adapterBaseTestUnit.js`)) {
-    const tFile = fs.readFileSync(`${adaptdir}/test/unit/adapterBaseTestUnit.js`, 'utf8');
-    tcodeCount += tFile.split('\n').length;
-    ttestCount += tFile.split('it(\'').length;
-  } else {
-    console.log('Missing - test/unit/adapterBaseTestUnit.js');
-  }
-  if (fs.existsSync(`${adaptdir}/test/unit/adapterTestUnit.js`)) {
-    const tFile = fs.readFileSync(`${adaptdir}/test/unit/adapterTestUnit.js`, 'utf8');
-    tcodeCount += tFile.split('\n').length;
-    ttestCount += tFile.split('it(\'').length;
-  } else {
-    console.log('Missing - test/unit/adapterTestUnit.js');
-  }
-  infoRes.testLines = tcodeCount;
-  infoRes.testCases = ttestCount;
-  infoRes.totalCodeLines = scodeCount + codeCount + tcodeCount;
+  infoRes.scriptLines = countLinesInFiles(utilFiles);
+
+  const adapterFiles = ['adapter.js', 'adapterBase.js'].map((f) => path.join(adaptdir, f));
+  infoRes.codeLines = countLinesInFiles(adapterFiles);
+
+  const testFiles = [
+    'test/integration/adapterTestBasicGet.js',
+    'test/integration/adapterTestConnectivity.js',
+    'test/integration/adapterTestIntegration.js',
+    'test/unit/adapterBaseTestUnit.js',
+    'test/unit/adapterTestUnit.js'
+  ].map((f) => path.join(adaptdir, f));
+  infoRes.testLines = countLinesInFiles(testFiles);
+  infoRes.testCases = countTestsInFiles(testFiles);
+
+  infoRes.totalCodeLines = infoRes.scriptLines + infoRes.codeLines + infoRes.testLines;
 
   if (fs.existsSync(`${adaptdir}/pronghorn.json`)) {
     // Read the entity schema from the file system
@@ -203,4 +148,9 @@ function adapterInfo() {
   fs.writeFileSync(`${adaptdir}/report/adapterInfo.json`, JSON.stringify(infoRes, null, 2));
 }
 
-adapterInfo();
+try {
+  adapterInfo();
+} catch (err) {
+  console.error(err.message);
+  process.exit();
+}

package/utils/argParser.js

@@ -0,0 +1,44 @@
+const customLevels = {
+  spam: 6,
+  trace: 5,
+  debug: 4,
+  info: 3,
+  warn: 2,
+  error: 1,
+  none: 0
+};
+
+function parseArgs(argv = process.argv) {
+  let properties = null;
+  let logLevel = 'none';
+  let maxCalls = 5;
+  let host = null;
+
+  argv.forEach((val) => {
+    if (val.startsWith('--PROPS=')) {
+      // get the properties
+      const inputVal = val.split('=')[1];
+      properties = JSON.parse(inputVal);
+    } else if (val.startsWith('--LOG=')) {
+      // get the desired log level
+      const level = val.split('=')[1];
+      // validate the log level is supported, if so set it
+      if (Object.hasOwnProperty.call(customLevels, level)) {
+        logLevel = level;
+      }
+    } else if (val.startsWith('--MAXCALLS=')) {
+      const override = parseInt(val.split('=')[1], 10);
+      if (!Number.isNaN(override) && override > 0) {
+        maxCalls = override;
+      }
+    } else if (val.startsWith('--HOST=')) {
+      [, host] = val.split('=');
+    }
+  });
+
+  return {
+    properties, logLevel, maxCalls, host
+  };
+}
+
+module.exports = { parseArgs };

package/utils/logger.js

@@ -0,0 +1,26 @@
+// utils/logger.js
+const winston = require('winston');
+const { parseArgs } = require('./argParser');
+
+const customLevels = {
+  spam: 6,
+  trace: 5,
+  debug: 4,
+  info: 3,
+  warn: 2,
+  error: 1,
+  none: 0
+};
+
+// Only set global logger if it doesn't already exist (i.e., not provided by app)
+if (!global.log) {
+  const { logLevel = 'info' } = parseArgs();
+
+  global.log = winston.createLogger({
+    level: logLevel,
+    levels: customLevels,
+    transports: [new winston.transports.Console()]
+  });
+}
+
+module.exports = global.log;

package/utils/artifactize.js

@@ -1,146 +0,0 @@
-#!/usr/bin/env node
-/* @copyright Itential, LLC 2019 */
-
-const path = require('path');
-const fs = require('fs-extra');
-
-async function createBundle(adapterOldDir) {
-  // set directories
-  const artifactDir = path.join(adapterOldDir, '../artifactTemp');
-  const workflowsDir = path.join(adapterOldDir, 'workflows');
-
-  // read adapter's package and set names
-  const adapterPackage = fs.readJSONSync(path.join(adapterOldDir, 'package.json'));
-  const originalName = adapterPackage.name.substring(adapterPackage.name.lastIndexOf('/') + 1);
-  const shortenedName = originalName.replace('adapter-', '');
-  const artifactName = originalName.replace('adapter', 'bundled-adapter');
-
-  const adapterNewDir = path.join(artifactDir, 'bundles', 'adapters', originalName);
-  fs.ensureDirSync(adapterNewDir);
-
-  const ops = [];
-
-  // copy old adapterDir to bundled hierarchy location
-  ops.push(() => fs.copySync(adapterOldDir, adapterNewDir));
-
-  // copy readme
-  ops.push(() => fs.copySync(path.join(adapterOldDir, 'README.md'), path.join(artifactDir, 'README.md')));
-
-  // copy changelog
-  if (fs.existsSync(path.join(adapterOldDir, 'CHANGELOG.md'))) {
-    ops.push(() => fs.copySync(path.join(adapterOldDir, 'CHANGELOG.md'), path.join(artifactDir, 'CHANGELOG.md')));
-  }
-
-  // copy license
-  if (fs.existsSync(path.join(adapterOldDir, 'LICENSE'))) {
-    ops.push(() => fs.copySync(path.join(adapterOldDir, 'LICENSE'), path.join(artifactDir, 'LICENSE')));
-  }
-
-  // create package
-  const artifactPackage = {
-    name: artifactName,
-    version: adapterPackage.version,
-    description: `A bundled version of the ${originalName} to be used in adapter-artifacts for easy installation`,
-    scripts: {
-      test: 'echo "Error: no test specified" && exit 1',
-      deploy: 'npm publish --registry=http://registry.npmjs.org'
-    },
-    keywords: [
-      'IAP',
-      'artifacts',
-      'Itential',
-      'Pronghorn',
-      'Adapter',
-      'Adapter-Artifacts',
-      shortenedName
-    ],
-    author: 'Itential Artifacts',
-    license: 'Apache-2.0',
-    repository: adapterPackage.repository,
-    private: false,
-    devDependencies: {
-      r2: '^2.0.1',
-      ajv: '6.10.0',
-      'better-ajv-errors': '^0.6.1',
-      'fs-extra': '^7.0.1'
-    }
-  };
-
-  ops.push(() => fs.writeJSONSync(path.join(artifactDir, 'package.json'), artifactPackage, { spaces: 2 }));
-
-  // create manifest
-  const manifest = {
-    bundleName: originalName,
-    version: adapterPackage.version,
-    fingerprint: 'Some verifiable token',
-    createdEpoch: '1554836984020',
-    artifacts: [
-      {
-        id: `${shortenedName}-adapter`,
-        name: `${shortenedName}-adapter`,
-        type: 'adapter',
-        location: `/bundles/adapters/${originalName}`,
-        description: artifactPackage.description,
-        properties: {
-          entryPoint: false
-        }
-      }
-    ]
-  };
-
-  // add workflows into artifact
-  if (fs.existsSync(workflowsDir)) {
-    const workflowFileNames = fs.readdirSync(workflowsDir);
-
-    // if folder isnt empty and only file is not readme
-    if (workflowFileNames.length !== 0 && (!(workflowFileNames.length === 1 && workflowFileNames[0].split('.')[1] === 'md'))) {
-      // add workflows to correct location in bundle
-      ops.push(() => fs.copySync(workflowsDir, path.join(artifactDir, 'bundles', 'workflows')));
-
-      // add workflows to manifest
-      workflowFileNames.forEach((filename) => {
-        const [filenameNoExt, ext] = filename.split('.');
-        if (ext === 'json') {
-          manifest.artifacts.push({
-            id: `workflow-${filenameNoExt}`,
-            name: filenameNoExt,
-            type: 'workflow',
-            location: `/bundles/workflows/${filename}`,
-            description: 'Main entry point to artifact',
-            properties: {
-              entryPoint: false
-            }
-          });
-        }
-      });
-    }
-  }
-
-  ops.push(() => fs.writeJSONSync(path.join(artifactDir, 'manifest.json'), manifest, { spaces: 2 }));
-
-  // Run the commands in parallel
-  try {
-    await Promise.all(ops.map(async (op) => op()));
-  } catch (e) {
-    throw new Error(e);
-  }
-
-  const pathObj = {
-    bundlePath: artifactDir,
-    bundledAdapterPath: path.join(artifactDir, 'bundles', 'adapters', originalName)
-  };
-  return pathObj;
-}
-
-async function artifactize(entryPathToAdapter) {
-  const truePath = path.resolve(entryPathToAdapter);
-  const packagePath = path.join(truePath, 'package');
-  // remove adapter from package and move bundle in
-  const pathObj = await createBundle(packagePath);
-  const { bundlePath } = pathObj;
-  fs.removeSync(packagePath);
-  fs.moveSync(bundlePath, packagePath);
-  return 'Bundle successfully created and old folder system removed';
-}
-
-module.exports = { createBundle, artifactize };

package/utils/packModificationScript.js

@@ -1,35 +0,0 @@
-#!/usr/bin/env node
-/* @copyright Itential, LLC 2019 */
-
-const path = require('path');
-const { spawnSync } = require('child_process');
-const fs = require('fs-extra');
-const { createBundle } = require('./artifactize');
-
-const nodeEntryPath = path.resolve('.');
-createBundle(nodeEntryPath).then((pathObj) => {
-  const { bundlePath, bundledAdapterPath } = pathObj;
-  const npmIgnorePath = path.join(bundledAdapterPath, '.npmignore');
-  const adapterPackagePath = path.join(bundledAdapterPath, 'package.json');
-  const artifactPackagePath = path.join(bundlePath, 'package.json');
-
-  // remove node_modules from .npmIgnore so that node_modules are included in the resulting tar from npm pack
-  let npmIgnoreString;
-  if (fs.existsSync(npmIgnorePath)) {
-    npmIgnoreString = fs.readFileSync(npmIgnorePath, 'utf8');
-    npmIgnoreString = npmIgnoreString.replace('node_modules', '');
-    npmIgnoreString = npmIgnoreString.replace('\n\n', '\n');
-    fs.writeFileSync(npmIgnorePath, npmIgnoreString);
-  }
-
-  // add files to package so that node_modules are included in the resulting tar from npm pack
-  const adapterPackage = fs.readJSONSync(adapterPackagePath);
-  adapterPackage.files = ['*'];
-  fs.writeJSONSync(artifactPackagePath, adapterPackage, { spaces: 2 });
-  const npmResult = spawnSync('npm', ['pack', '-q', bundlePath], { cwd: path.resolve(bundlePath, '..') });
-  if (npmResult.status === 0) {
-    fs.removeSync(bundlePath);
-    console.log('Bundle folder removed');
-  }
-  console.log('Script successful');
-});