Skip to content
This repository has been archived by the owner on Sep 3, 2024. It is now read-only.

INT-2714 - Fix for hardware mapping #35

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

eXtremeX
Copy link
Contributor

@eXtremeX eXtremeX commented Dec 21, 2022

The Snipe-IT allows us to use particular host name that's filled with sample data (https://develop.snipeitapp.com). Once we used that we noticed that not all hardware responses contain the values we had assigned to manufacturer, make and/or model. The integration was erroring out for those.

We also noticed that convertHardware function isn't able to return macAddress nor hardwareId so we deleted those two branches.

  • Assigned unknown value if hardware manufacturer, make or model field
    is undefined.
  • Fixed part corresponding to iterating hardware assigned user.
  • Cleaned up code for creating hardware related mapped relationships (we can
    only access the serial value).

@eXtremeX eXtremeX requested a review from a team as a code owner December 21, 2022 08:06
@eXtremeX eXtremeX force-pushed the bugfix/hardware-mapping branch from 270ed0c to d0cce29 Compare December 21, 2022 08:59
@eXtremeX eXtremeX changed the title Bugfix/hardware mapping INT-2714 - Fix for hardware mapping Dec 21, 2022
@@ -75,10 +90,12 @@ export function mapHardwareRelationship(
sourceEntityKey: account._key,
targetFilterKeys: [['_class', filterKey]],
targetEntity: {
...convertProperties(hardware),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to verify that the properties that were being produce here are not being used by customers.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants