@itentialopensource/adapter-infoblox_netmri/report/adapter-openapi.yaml

This adapter integrates with system described as: Infoblox NetMRI

openapi: 3.0.0
info:
  title: Infoblox NetMRI
  contact: {}
  version: '3.3'
servers:
- url: https://netmri.comp.com/api/3.3
  variables: {}
paths:
  /devices/show:
    get:
      tags:
      - Devices
      summary: devicesShow
      description: ''
      operationId: devicesShow
      parameters:
      - name: DeviceID
        in: query
        description: An internal NetMRI identifier for the device.
        required: true
        style: form
        explode: true
        schema:
          type: integer
          format: int64
          example: 509884177951627265
      - name: methods
        in: query
        description: 'A comma-delimited list of device methods. The listed methods will be called on each device returned and included in the output. Available methods are: SwitchingInd, RoutingInd, DeviceSAAVersion, DeviceRebootTime, DeviceContextName, DeviceCommunitySecure, DeviceRank, DeviceCommunity, DeviceFirstOccurrence, group, parent_device, gateway_device, running_config, running_config_text, saved_config, saved_config_text, running_config_diff, saved_config_diff, virtual_child_count, asset_type, device_setting, data_collection_status, control_capabilities, network_name, interfaces, issue_details, device_routes, device_physicals, if_addrs, config_revisions, detected_changes, device_ports, cap_description_ind, cap_admin_status_ind, cap_vlan_assignment_ind, cap_voice_vlan_ind, cap_net_provisioning_ind, cap_net_vlan_provisioning_ind, cap_net_deprovisioning_ind, cap_description_na_reason, cap_admin_status_na_reason, cap_vlan_assignment_na_reason, cap_voice_vlan_na_reason, cap_net_provisioning_na_reason, cap_net_vlan_provisioning_na_reason, cap_net_deprovisioning_na_reason, meta, data_source.'
        style: form
        explode: true
        schema:
          type: array
          items: {}
      - name: include
        in: query
        description: 'A comma-delimited list of associated object types to include in the output. The listed associations will be returned as outputs named according to the association name (see outputs below). Available includes are: parent_device, device_setting, data_collection_status, interfaces, issue_details, device_routes, device_physicals, if_addrs, config_revisions, detected_changes, device_ports, meta, data_source.'
        style: form
        explode: true
        schema:
          type: array
          items: {}
      responses:
        '200':
          description: ''
          headers: {}
          content: {}
      deprecated: false
  /devices/index:
    get:
      tags:
      - Devices
      summary: devicesIndex
      description: Lists the available devices.  Any of the inputs listed may be be used to narrow the list; other inputs will be ignored. Of the various ways to query lists, using this method is most efficient.
      operationId: devicesIndex
      parameters:
      - name: select
        in: query
        description: comma-delimited list of attributes to return
        style: form
        explode: true
        schema:
          type: array
          items: {}
      responses:
        '200':
          description: ''
          headers: {}
          content: {}
      deprecated: false
  /device_groups/index:
    get:
      tags:
      - DeviceGroups
      summary: deviceGroupsIndex
      description: Lists the available device groups. Any of the inputs listed may be be used to narrow the list; other inputs will be ignored. Of the various ways to query lists, using this method is most efficient.
      operationId: deviceGroupsIndex
      parameters: []
      responses:
        '200':
          description: ''
          headers: {}
          content: {}
      deprecated: false
  /interfaces/search:
    get:
      tags:
      - Interfaces
      summary: interfacesSearch
      description: Lists the available interfaces matching the input criteria. This method provides a more flexible search interface than the index method, but searching using this method is more demanding on the system and will not perform to the same level as the index method. The input fields will be used as in the index method to filter the result, along with the optional query string and XML filter described in the documentation.
      operationId: interfacesSearch
      parameters:
      - name: GroupID
        in: query
        description: A comma-delimited list of internal NetMRI identifier(s) of the device group(s) to which to limit the results.
        style: form
        explode: true
        schema:
          type: array
          items: {}
      responses:
        '200':
          description: ''
          headers: {}
          content: {}
      deprecated: false
components:
  securitySchemes:
    httpBasic:
      type: http
      scheme: basic
security:
- httpBasic: []
tags:
- name: Devices
  description: The devices discovered by NetMRI
- name: DeviceGroups
  description: Collections of devices
- name: Interfaces
  description: ''