@itentialopensource/adapter-netbox_v33 2.1.7 → 2.1.8

package/AUTH.md

@@ -1,39 +1,35 @@
-## Authenticating Netbox_v33 Adapter 
+## Authenticating NetBox Adapter 
 
-This document will go through the steps for authenticating the Netbox_v33 adapter with Basic Authentication. 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://www.itential.com/automation-platform/integrations/adapters-resources/authentication/" target="_blank">HERE</a>. 
+This document will go through the steps for authenticating the NetBox adapter with authentication methods we have worked with in the past. 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>. 
 
-### Basic Authentication
-The Netbox_v33 adapter requires Basic Authentication. If you change authentication methods, you should change this section accordingly and merge it back into the adapter repository.
+Companies periodically change authentication methods to provide better security. As this happens this section should be updated and contributed/merge back into the adapter repository.
+
+### Static Token (APIKEY) Authentication
+The NetBox adapter requires Static Token (APIKEY) 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 Netbox_v33 server and that it is running
+1. Ensure you have access to a NetBox 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
 3. Use the properties below for the ```properties.authentication``` field
 ```json
 "authentication": {
-  "auth_method": "basic user_password",
-  "username": "<username>",
-  "password": "<password>",
-  "token": "",
-  "token_timeout": 1800000,
-  "token_cache": "local",
-  "invalid_token_error": 401,
+  "auth_method": "static_token",
+  "token": "<token>",
   "auth_field": "header.headers.Authorization",
-  "auth_field_format": "Basic {b64}{username}:{password}{/b64}",
-  "auth_logging": false,
-  "client_id": "",
-  "client_secret": "",
-  "grant_type": ""
+  "auth_field_format": "Token {token}",
+  "auth_logging": false
 }
 ```
+you can leave all of the other properties in the authentication section, they will not be used when the auth_method is static_token.<br>
 4. Restart the adapter. If your properties were set correctly, the adapter should go online. 
 
 ### Troubleshooting
-- Make sure you copied over the correct username and password.
+- Make sure you copied over the correct token.
 - Turn on debug level logs for the adapter in IAP Admin Essentials.
 - Turn on auth_logging for the adapter in IAP Admin Essentials (adapter properties).
 - Investigate the logs - in particular:
   - The FULL REQUEST log to make sure the proper headers are being sent with the request.
   - The FULL BODY log to make sure the payload is accurate.
   - The CALL RETURN log to see what the other system is telling us.
+- 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.
 - Remember when you are done to turn auth_logging off as you do not want to log credentials.

package/BROKER.md

@@ -22,18 +22,25 @@ Below is an example of how you may set up the properties for this call.
   {
     "path": "/{org}/get/devices",
     "method": "GET",
+    "pagination": {
+      "offsetVar": "",
+      "limitVar": "",
+      "incrementBy": "limit",
+      "requestLocation": "query"
+    },
     "query": {},
     "body": {},
     "headers": {},
     "handleFailure": "ignore",
+    "responseDataKey": "",
     "requestFields": {
       "org": "555"
     },
     "responseFields": {
-      "name": "host",
-      "ostype": "os",
+      "name": "{hostField}",
+      "ostype": "{osField}",
       "ostypePrefix": "system-",
-      "ipaddress": "attributes.ipaddr",
+      "ipaddress": "{attributes.ipaddr}",
       "port": "443"
     }
   },
@@ -44,16 +51,17 @@ Below is an example of how you may set up the properties for this call.
     "body": {},
     "headers": {},
     "handleFailure": "ignore",
+    "responseDataKey": "",
     "requestFields": {
       "org": "777"
     },
     "responseFields": {
-      "name": "host",
-      "ostype": "os",
+      "name": "{hostField}",
+      "ostype": "{osField}",
       "ostypePrefix": "system-",
-      "ipaddress": "attributes.ipaddr",
+      "ipaddress": "{attributes.ipaddr}",
       "port": "443",
-      "myorg": "org"
+      "myorg": "{orgField}"
     }
   }
 ]
@@ -88,12 +96,13 @@ Below is an example of how you may set up the properties for this call.
     "headers": {},
     "handleFailure": "ignore",
     "statusValue": "online",
+    "responseDataKey": "",
     "requestFields": {
-      "org": "myorg",
-      "id": "name"
+      "org": "{myorg}",
+      "id": "{name}"
     },
     "responseFields": {
-      "status": "status"
+      "status": "{status}"
     }
   }
 ]
@@ -129,9 +138,10 @@ Below is an example of how you may set up the properties for this call.
     "body": {},
     "headers": {},
     "handleFailure": "ignore",
+    "responseDataKey": "",
     "requestFields": {
-      "org": "myorg",
-      "id": "name"
+      "org": "{myorg}",
+      "id": "{name}"
     }
     "responseFields": {}
   },
@@ -142,8 +152,9 @@ Below is an example of how you may set up the properties for this call.
     "body": {},
     "headers": {},
     "handleFailure": "ignore",
+    "responseDataKey": "",
     "requestFields": {
-      "org": "myorg"
+      "org": "{myorg}"
     }
     "responseFields": {}
   }
@@ -178,17 +189,18 @@ Below is an example of how you may set up the properties for this call.
     "body": {},
     "headers": {},
     "handleFailure": "ignore",
+    "responseDataKey": "",
     "requestFields": {
-      "org": "myorg",
-      "id": "name"
+      "org": "{myorg}",
+      "id": "{name}"
     },
     "responseFields": {
-      "name": "host",
-      "ostype": "os",
+      "name": "{hostField}",
+      "ostype": "{osField}",
       "ostypePrefix": "system-",
-      "ipaddress": "attributes.ipaddr",
+      "ipaddress": "{attributes.ipaddr}",
       "port": "443",
-      "myorg": "org"
+      "myorg": "{orgField}"
     }
   }
 ]

package/CALLS.md

@@ -19,7 +19,7 @@ These are adapter methods that IAP or you might use. There are some other method
   </tr>
   <tr>
     <td style="padding:15px">healthCheck(callback)</td>
-    <td style="padding:15px">This call ensures that the adapter can communicate with Netbox_v33. The actual call that is used is defined in the adapter properties and .system entities action.json file.</td>
+    <td style="padding:15px">This call ensures that the adapter can communicate with Adapter for NetBox. The actual call that is used is defined in the adapter properties and .system entities action.json file.</td>
     <td style="padding:15px">No</td>
   </tr>
   <tr>
@@ -29,7 +29,7 @@ These are adapter methods that IAP or you might use. There are some other method
   </tr>
   <tr>
     <td style="padding:15px">encryptProperty(property, technique, callback)</td>
-    <td style="padding:15px">This call will take the provided property and technique, and return the property encrypted with the technique. This allows the property to be used in the adapterProps section for the credential password so that the password does not have to be in clear text. The adapter will decrypt the property as needed for communications with Netbox_v33.</td>
+    <td style="padding:15px">This call will take the provided property and technique, and return the property encrypted with the technique. This allows the property to be used in the adapterProps section for the credential password so that the password does not have to be in clear text. The adapter will decrypt the property as needed for communications with Adapter for NetBox.</td>
     <td style="padding:15px">No</td>
   </tr>
   <tr>
@@ -37,11 +37,6 @@ These are adapter methods that IAP or you might use. There are some other method
     <td style="padding:15px">This call provides the ability to update the adapter configuration from IAP - includes actions, schema, mockdata and other configurations.</td>
     <td style="padding:15px">Yes</td>
   </tr>
-  <tr>
-    <td style="padding:15px">iapFindAdapterPath(apiPath, callback)</td>
-    <td style="padding:15px">This call provides the ability to see if a particular API path is supported by the adapter.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
   <tr>
     <td style="padding:15px">iapSuspendAdapter(mode, callback)</td>
     <td style="padding:15px">This call provides the ability to suspend the adapter and either have requests rejected or put into a queue to be processed after the adapter is resumed.</td>
@@ -57,12 +52,16 @@ These are adapter methods that IAP or you might use. There are some other method
     <td style="padding:15px">This call will return the requests that are waiting in the queue if throttling is enabled.</td>
     <td style="padding:15px">Yes</td>
   </tr>
+  <tr>
+    <td style="padding:15px">iapFindAdapterPath(apiPath, callback)</td>
+    <td style="padding:15px">This call provides the ability to see if a particular API path is supported by the adapter.</td>
+    <td style="padding:15px">Yes</td>
+  </tr>
   <tr>
     <td style="padding:15px">iapTroubleshootAdapter(props, persistFlag, adapter, callback)</td>
     <td style="padding:15px">This call can be used to check on the performance of the adapter - it checks connectivity, healthcheck and basic get calls.</td>
     <td style="padding:15px">Yes</td>
   </tr>
-
   <tr>
     <td style="padding:15px">iapRunAdapterHealthcheck(adapter, callback)</td>
     <td style="padding:15px">This call will return the results of a healthcheck.</td>
@@ -83,6 +82,21 @@ These are adapter methods that IAP or you might use. There are some other method
     <td style="padding:15px">This call will push the adapter configuration from the entities directory into the Adapter or IAP Database.</td>
     <td style="padding:15px">Yes</td>
   </tr>
+  <tr>
+    <td style="padding:15px">iapDeactivateTasks(tasks, callback)</td>
+    <td style="padding:15px">This call provides the ability to remove tasks from the adapter.</td>
+    <td style="padding:15px">Yes</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">iapActivateTasks(tasks, callback)</td>
+    <td style="padding:15px">This call provides the ability to add deactivated tasks back into the adapter.</td>
+    <td style="padding:15px">Yes</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">iapExpandedGenericAdapterRequest(metadata, uriPath, restMethod, pathVars, queryData, requestBody, addlHeaders, callback)</td>
+    <td style="padding:15px">This is an expanded Generic Call. The metadata object allows us to provide many new capabilities within the generic request.</td>
+    <td style="padding:15px">Yes</td>
+  </tr>
   <tr>
     <td style="padding:15px">genericAdapterRequest(uriPath, restMethod, queryData, requestBody, addlHeaders, callback)</td>
     <td style="padding:15px">This call allows you to provide the path to have the adapter call. It is an easy way to incorporate paths that have not been built into the adapter yet.</td>
@@ -94,23 +108,46 @@ These are adapter methods that IAP or you might use. There are some other method
     <td style="padding:15px">Yes</td>
   </tr>
   <tr>
-    <td style="padding:15px">iapHasAdapterEntity(entityType, entityId, callback)</td>
-    <td style="padding:15px">This call verifies the adapter has the specific entity.</td>
-    <td style="padding:15px">No</td>
+    <td style="padding:15px">iapRunAdapterLint(callback)</td>
+    <td style="padding:15px">Runs lint on the addapter and provides the information back.</td>
+    <td style="padding:15px">Yes</td>
   </tr>
   <tr>
-    <td style="padding:15px">iapVerifyAdapterCapability(entityType, actionType, entityId, callback)</td>
-    <td style="padding:15px">This call verifies the adapter can perform the provided action on the specific entity.</td>
-    <td style="padding:15px">No</td>
+    <td style="padding:15px">iapRunAdapterTests(callback)</td>
+    <td style="padding:15px">Runs baseunit and unit tests on the adapter and provides the information back.</td>
+    <td style="padding:15px">Yes</td>
   </tr>
   <tr>
-    <td style="padding:15px">iapUpdateAdapterEntityCache()</td>
-    <td style="padding:15px">This call will update the entity cache.</td>
-    <td style="padding:15px">No</td>
+    <td style="padding:15px">iapGetAdapterInventory(callback)</td>
+    <td style="padding:15px">This call provides some inventory related information about the adapter.</td>
+    <td style="padding:15px">Yes</td>
   </tr>
 </table>
 <br>
+  
+### Adapter Cache Calls
 
+These are adapter methods that are used for adapter caching. If configured, the adapter will cache based on the interval provided. However, you can force a population of the cache manually as well.
+
+<table border="1" class="bordered-table">
+  <tr>
+    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Method Signature</span></th>
+    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
+    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Workflow?</span></th>
+  </tr>
+  <tr>
+    <td style="padding:15px">iapPopulateEntityCache(entityTypes, callback)</td>
+    <td style="padding:15px">This call populates the adapter cache.</td>
+    <td style="padding:15px">Yes</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">iapRetrieveEntitiesCache(entityType, options, callback)</td>
+    <td style="padding:15px">This call retrieves the specific items from the adapter cache.</td>
+    <td style="padding:15px">Yes</td>
+  </tr>
+</table>
+<br>
+  
 ### Adapter Broker Calls
 
 These are adapter methods that are used to integrate to IAP Brokers. This adapter currently supports the following broker calls.
@@ -129,32 +166,31 @@ These are adapter methods that are used to integrate to IAP Brokers. This adapte
   <tr>
     <td style="padding:15px">getDevice(deviceName, callback)</td>
     <td style="padding:15px">This call returns the details of the requested device.</td>
-    <td style="padding:15px">Yes</td>
+    <td style="padding:15px">No</td>
   </tr>
   <tr>
     <td style="padding:15px">getDevicesFiltered(options, callback)</td>
     <td style="padding:15px">This call returns the list of devices that match the criteria provided in the options filter.</td>
-    <td style="padding:15px">Yes</td>
+    <td style="padding:15px">No</td>
   </tr>
   <tr>
     <td style="padding:15px">isAlive(deviceName, callback)</td>
     <td style="padding:15px">This call returns whether the device status is active</td>
-    <td style="padding:15px">Yes</td>
+    <td style="padding:15px">No</td>
   </tr>
   <tr>
     <td style="padding:15px">getConfig(deviceName, format, callback)</td>
     <td style="padding:15px">This call returns the configuration for the selected device.</td>
-    <td style="padding:15px">Yes</td>
+    <td style="padding:15px">No</td>
   </tr>
   <tr>
     <td style="padding:15px">iapGetDeviceCount(callback)</td>
     <td style="padding:15px">This call returns the count of devices.</td>
-    <td style="padding:15px">Yes</td>
+    <td style="padding:15px">No</td>
   </tr>
 </table>
 <br>
 
-
 ### Specific Adapter Calls
 
 Specific adapter calls are built based on the API of the Netbox_v33. The Adapter Builder creates the proper method comments for generating JS-DOC for the adapter. This is the best way to get information on the calls.

package/CHANGELOG.md

@@ -1,4 +1,12 @@
 
+## 2.1.8 [07-23-2024]
+
+* add timeout to fix unit
+
+See merge request itentialopensource/adapters/inventory/adapter-netbox_v33!13
+
+---
+
 ## 2.1.7 [05-01-2024]
 
 * Patch/adapt 3335

package/PROPERTIES.md

@@ -97,6 +97,7 @@ This section defines **all** the properties that are available for the adapter,
         }
       },
       "devicebroker": {
+        "enabled": false,
         "getDevice": [
           {
             "path": "/call/to/get/device/details",
@@ -580,6 +581,10 @@ The device broker section defines the properties used integrate Netbox_v33 to th
     <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
     <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
   </tr>
+  <tr>
+    <td style="padding:15px">enabled</td>
+    <td style="padding:15px">Whether or not the device broker calls have been mapped.</td>
+  </tr>
   <tr>
     <td style="padding:15px">getDevice</td>
     <td style="padding:15px">The array of calls used to get device details for the broker</td>

package/README.md

@@ -4,29 +4,49 @@
 
 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.
 
-- [Overview](./SUMMARY.md)
-- [Versioning](#versioning)
-- [Supported IAP Versions](#supported-iap-versions)
-- [Getting Started](#getting-started)
-  - [Helpful Background Information](#helpful-background-information)
-  - [Prerequisites](#prerequisites)
-  - [How to Install](#how-to-install)
-  - [Testing](#testing)
-- [Configuration](./PROPERTIES.md)
-- [Using this Adapter](./CALLS.md)
+- [Specific to this Adapter](#specific-to-this-adapter)
   - [Authentication](./AUTH.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)
+  - [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 IAP Versions](#supported-iap-versions)
+  - [Getting Started](#getting-started)
+    - [Helpful Background Information](#helpful-background-information)
+    - [Prerequisites](#prerequisites)
+    - [How to Install](#how-to-install)
+    - [Testing](#testing)
+  - [Configuration](./PROPERTIES.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)
+
+
+## Specific to this Adapter
 
-## [Overview](./SUMMARY.md)
+### [Authentication](./AUTH.md)
+
+### [Sample Properties](./sampleProperties.json)
+
+<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
 
-## Versioning
+### [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 IAP 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>.
 
@@ -34,7 +54,7 @@ Any release prior to 1.0.0 is a pre-release. Initial builds of adapters are gene
 
 Release notes can be viewed in CHANGELOG.md.
 
-## Supported IAP Versions
+### Supported IAP Versions
 
 Itential Product adapters are built for particular versions of IAP and packaged with the versions they work with. 
 
@@ -42,11 +62,11 @@ Itential opensource adapter as well as custom adapters built with the Itential A
 
 Many of the scripts that come with all adapters built using the Itential Adapter Builder do have some dependencies on IAP or the IAP database schema and so it is possible these scripts could stop working in different versions of IAP. If you notify Itential of any issues, the Adapter Team will attempt to fix the scripts for newer releases of IAP.
 
-## Getting Started
+### 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
+#### 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:
 
@@ -67,7 +87,7 @@ 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
+#### Prerequisites
 
 The following is a list of required packages for installation on the system the adapter will run on:
 
@@ -154,7 +174,7 @@ eslint-plugin-json
 testdouble
 ```
 
-### How to Install
+#### How to Install
 
 1. Set up the name space location in your IAP node_modules.
 
@@ -167,8 +187,8 @@ if the @itentialopensource directory does not exist, create it:
 2. Clone/unzip/tar the adapter into your IAP environment.
 
 ```bash
-cd \@itentialopensource
-git clone git@gitlab.com:\@itentialopensource/adapters/adapter-netbox_v33
+cd @itentialopensource
+git clone git@gitlab.com:@itentialopensource/adapters/adapter-netbox_v33
 or
 unzip adapter-netbox_v33.zip
 or
@@ -196,30 +216,11 @@ systemctl restart pronghorn
 
 7. Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
 
-
-For an easier install of the adapter use npm run adapter:install, it will install the adapter in IAP. Please note that it can be dependent on where the adapter is installed and on the version of IAP so it is subject to fail. If using this, you can replace step 3-5 above with these:
-
-3. Install adapter dependencies and check the adapter.
-
-```bash
-cd adapter-netbox_v33
-npm run adapter:install
-```
-
-4. Restart IAP
-
-```bash
-systemctl restart pronghorn
-```
-
-5. Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
-
-
-### Testing
+#### 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
 
 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.
 
@@ -232,7 +233,7 @@ 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
+##### 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 Netbox_v33. 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.
 
@@ -247,7 +248,7 @@ 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
 
 Integration Testing requires connectivity to Netbox_v33. 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.
 
@@ -263,23 +264,19 @@ Test should also be written to clean up after themselves. However, it is importa
 
 > **Reminder**: Do not check in code with actual credentials to systems.
 
-## [Configuration](./PROPERTIES.md)
-
-## [Using this Adapter](./CALLS.md)
-
-### [Authentication](./AUTH.md)
+### [Configuration](./PROPERTIES.md)
 
-## Additional Information
+### Additional Information
 
-### [Enhancements](./ENHANCE.md)
+#### [Enhancements](./ENHANCE.md)
 
-### [Contributing](./CONTRIBUTING.md)
+#### [Contributing](./CONTRIBUTING.md)
 
-### Helpful Links
+#### Helpful Links
 
 <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter Technical Resources</a>
 
-### Node Scripts
+#### Node Scripts
 
 There are several node scripts that now accompany the adapter. These scripts are provided to make several activities easier. Many of these scripts can have issues with different versions of IAP as they have dependencies on IAP and Mongo. If you have issues with the scripts please report them to the Itential Adapter Team. Each of these scripts are described below.
 
@@ -331,9 +328,9 @@ There are several node scripts that now accompany the adapter. These scripts are
 </table>
 <br>
 
-## [Troubleshoot](./TROUBLESHOOT.md)
+### [Troubleshoot](./TROUBLESHOOT.md)
 
-## License and Maintainers
+### License and Maintainers
 
 ```text
 Itential Product Adapters are maintained by the Itential Product Team.
@@ -341,6 +338,6 @@ Itential OpenSource Adapters are maintained by the Itential Adapter Team and the
 Custom Adapters are maintained by other sources.
 ```
 
-## Product License
+### Product License
 
 [Apache 2.0](./LICENSE)

package/SYSTEMINFO.md

@@ -1,11 +1,26 @@
-# Netbox_v33
+# NetBox
 
-Vendor: Netbox_v33
-Homepage: https://Netbox_v33.com/
+Vendor: NetBox
+Homepage: https://netbox.dev/
 
-Product: Netbox_v33
-Product Page: https://Netbox_v33.com/
+Product: NetBox
+Product Page: https://netbox.dev/
 
 ## Introduction
+We classify NetBox into the Inventory domain because it contains an inventory of devices, assets, network discovery and topology information.
 
-## Additional Product Documentation
+"NetBox provides the ideal "source of truth" to power network automation."
+
+## Why Integrate
+The NetBox adapter from Itential is used to integrate the Itential Automation Platform (IAP) with NetBox. With this adapter you have the ability to perform operations such as:
+
+- Add and Remove Inventory Items.
+- Create Subnet
+- Create IP Record
+- Get Next Available IP
+- Get Circuit
+- Get L2VPN
+- Get Device
+
+## Additional Product Documentation
+The [API documents for Netbox](https://demo.netbox.dev/)

package/TAB1.md

@@ -2,4 +2,15 @@
 
 This adapter is used to integrate the Itential Automation Platform (IAP) with the Netbox_v33 System. The API that was used to build the adapter for Netbox_v33 is usually available in the report directory of this adapter. The adapter utilizes the Netbox_v33 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.
 
+## Details 
+The NetBox adapter from Itential is used to integrate the Itential Automation Platform (IAP) with NetBox. With this adapter you have the ability to perform operations such as:
+
+- Add and Remove Inventory Items.
+- Create Subnet
+- Create IP Record
+- Get Next Available IP
+- Get Circuit
+- Get L2VPN
+- Get Device
+
 For further technical details on how to install and use this adapter, please click the Technical Documentation tab.