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

add blueprint entity #27

Merged
merged 9 commits into from
Jul 12, 2024
Merged

add blueprint entity #27

merged 9 commits into from
Jul 12, 2024

Conversation

mikiodehartj1
Copy link
Contributor

Description

Thank you for contributing to a JupiterOne integration!

Please include a summary of the change and which issue is fixed. Please also
include relevant motivation and context. List any dependencies that are required
for this change.

Summary

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.

@mikiodehartj1 mikiodehartj1 requested a review from a team as a code owner July 2, 2024 17:11
@mikiodehartj1
Copy link
Contributor Author

Relationship Mappings are outlined here:
https://jupiterone.atlassian.net/browse/INT-11237

@@ -38,6 +38,7 @@
"@jupiterone/integration-sdk-core": "^13.2.0"
},
"devDependencies": {
"@babel/preset-typescript": "^7.17.12",
Copy link
Contributor

Choose a reason for hiding this comment

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

Fixed linting

RonaldEAM
RonaldEAM previously approved these changes Jul 12, 2024
@VDubber VDubber merged commit ee75e0a into main Jul 12, 2024
9 checks passed
@VDubber VDubber deleted the KNO-413 branch July 12, 2024 22:12
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