Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@jupiterone/integration-sdk-http-client

Package Overview
Dependencies
Maintainers
0
Versions
141
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@jupiterone/integration-sdk-http-client - npm Package Versions

1
15

8.21.0

Diff

Changelog

Source

8.21.0 - 2021-07-20

Added

  • Added IntegrationInfoEventName.Results and IntegrationWarnEventName.MissingEntity.
jupiterone-dev
published 8.20.0 •

Changelog

Source

8.20.0 - 2021-07-16

Added

  • Introduce beforeAddRelationship hook into IntegrationInvocationConfig. See the development documentation for more information on its usage.
jupiterone-dev
published 8.19.0 •

Changelog

Source

[8.19.0] - 2022-07-07

Added

  • New j1-integration generate-integration-graph-schema CLI command added
Usage: j1-integration generate-integration-graph-schema [options]

generate integration graph metadata summary from step metadata

Options:
  -o, --output-file <path>        project relative path to generated integration graph schema file
  -p, --project-path <directory>  path to integration project directory (default: "{CWD}")
  -h, --help                      display help for command
jupiterone-dev
published 8.18.1 •

Changelog

Source

[8.18.1] - 2022-07-05

Changed

  • Bumped @jupiterone/data-model@v0.51.0
jupiterone-dev
published 8.18.0 •

Changelog

Source

[8.18.0] - 2022-07-01

Added

  • Added the ability to specify a reason for why a step is disabled. This can be set in the StepStartState interface using the DisabledStepReason enum. Valid reasons include: PERMISSION, CONFIG, BETA, and NONE. NONE is the equivalent to not specifying a reason. If NONE or undefined are specified, logging to the job event log is disabled. Here is an example of usage:
{
  ['fetch-prs']: {
    disabled: false
  },
  ['fetch-issues']: {
    disabled: !scopes.repoIssues,
    disabledReason: DisabledStepReason.PERMISSION
  }
}

Sample text output:

Skipped step "Fetch Issues". The required permission was not provided to perform this step.
Skipped step "Fetch Issues". This step is disabled via configuration. Please contact support to enabled.
Skipped step "Fetch Issues". Beta feature, please contact support to enable.
jupiterone-dev
published 8.17.0 •

Changelog

Source

[8.17.0] - 2022-06-29

Added

  • Added ability to set a separate uploadRelationshipsBatchSize. sync and run commands can specify the relationship-specific batch size with the -ur or --upload-relationship-batch-size flags. Existing behavior remains the same. If a uploadBatchSize is set, but no uploadRelationshipsBatchSize, then relationships will be uploaded in batches of size uploadBatchSize.
jupiterone-dev
published 8.16.0 •

Changelog

Source

[8.16.0] - 2022-06-27

Added

  • Added an optional encounteredEntityKeys property on .toMatchStepMetadata() to verify that any relationship _fromEntityKey and _toEntityKey has actually been encountered in the job state.
jupiterone-dev
published 8.15.0 •

Changelog

Source

[8.15.0] - 2022-06-22

Changed

  • @jupiterone/data-model has been bumped to 0.50.0
jupiterone-dev
published 8.14.1 •

Changelog

Source

[8.14.1] - 2022-06-17

Added

  • j1-integration sync and run commands now have the option --upload-batch-size to specify how many objects to upload in each batch.
jupiterone-dev
published 8.14.0 •

Changelog

Source

[8.14.0] - 2022-06-13

Added

  • j1-integration now has the command visualize-dependencies to create a visualization of the integration's step dependencies.
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc