Adapters are scoped to a namespace, and the adapter must be installed in the directory that matches that namespace within theItential Platform node_modules directory. If the installed path does not match the namespace defined in the adapter files (such as package.json and pronghorn.json), the adapter will not load.
NewerItential Platform releases align namespace rules with npm conventions — uppercase letters are no longer valid in namespaces. An adapter with an uppercase namespace will still load, but you will not be able to set service instance configuration values inItential Platform Admin Essentials without first updating the namespace.
@itentialopensource — most open-source Itential adapters. Install to:
<IAP-Home>/node_modules/@itentialopensource/<adapter-name>
Example: /opt/itential/current/node_modules/@itentialopensource/adapter-aws_ec2
@itential — adapters bundled withItential Platform by default, including severalItential Platform authentication adapters (such as adapter-ldap) and specialized orchestration adapters (such as adapter-nso). Install to:
<IAP-Home>/node_modules/@itential/<adapter-name>
Example: /opt/itential/current/node_modules/@itential/adapter-nso
Custom namespaces — adapters built by Itential Professional Services or by customers may use their own namespace. Install to:
<IAP-Home>/node_modules/@<namespace>/<adapter-name>
Example: /opt/itential/current/node_modules/@mycompany/adapter-mycustomadapter
If the adapter is not installed in the correct directory, it will fail to load whenItential Platform is restarted.