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

Add Device and Users Steps #2

Merged
merged 6 commits into from
Mar 8, 2023
Merged

Add Device and Users Steps #2

merged 6 commits into from
Mar 8, 2023

Conversation

zemberdotnet
Copy link
Contributor

Description

Adding Device and Users steps to integration

Type of change

Please leave any irrelevant options unchecked.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to
    not work as expected)
  • This change requires a documentation update

Checklist

General Development Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Integration Development Checklist:

Please leave any irrelevant options unchecked.

  • I have checked for additional permissions required to call any new API
    endpoints, and have documented any additional permissions in
    jupiterone.md, where necessary.
  • My changes properly paginate the target service provider's API
  • My changes properly handle rate limiting of the target service provider's
    API
  • My new integration step is instrumented to execute in the correct order
    using dependsOn
  • I have referred to the
    JupiterOne data model
    to ensure that any new entities/relationships, and relevant properties,
    match the recommended model for this class of data
  • I have updated the CHANGELOG.md file to describe my changes
  • When changes include modifications to existing graph data ingestion, I've
    reviewed all existing managed questions referencing the entities,
    relationships, and their property names, to ensure those questions still
    function with my changes.

src/client.ts Show resolved Hide resolved
src/client.ts Show resolved Hide resolved
src/config.ts Outdated Show resolved Hide resolved
VDubber
VDubber previously approved these changes Mar 6, 2023
Copy link
Contributor

@VDubber VDubber left a comment

Choose a reason for hiding this comment

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

Few minor comments.

@VDubber
Copy link
Contributor

VDubber commented Mar 6, 2023

It'd be good to get account entity added and then a mapping in data-dictionary to root.

test/config.ts Outdated

export const integrationConfig: IntegrationConfig = {
clientId: process.env.CLIENT_ID || DEFAULT_CLIENT_ID,
clientSecret: process.env.CLIENT_SECRET || DEFAULT_CLIENT_SECRET,
device42Username: process.env.USERNAME || 'test',
Copy link
Contributor

Choose a reason for hiding this comment

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

Update USERNAME reference here too

Copy link
Contributor

Choose a reason for hiding this comment

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

nit: consider using ?? instead of logical OR ||

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated here as well. I completely missed it!

test/config.ts Outdated Show resolved Hide resolved
@zemberdotnet zemberdotnet merged commit 394671c into main Mar 8, 2023
@zemberdotnet zemberdotnet deleted the int-add-device-users branch March 8, 2023 14:06
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.

2 participants