@jupiterone/integration-sdk-core
Advanced tools
Changelog
3.5.0 - 2020-10-03
@jupiterone/data-model
to version 0.13.0.Changelog
3.3.0 - 2020-09-25
j1-integration visualize-type
command generates metadata graph of types--disable-schema-validation
flag to j1-integration collect
command.setData
input to createMockJobState()
test util.shouldReportErrorToOperator
function for integration runtime
environments to check whether an Error
is of a type that need not be alerted
to deployment operators. All Error
s other than those only an end user can
resolve should be reported.ToMatchGraphObjectSchemaParams.schema
property optional in jest matcher.AdditionalRelationshipProperties
to not allow
Array or Object types.Changelog
3.1.0 - 2020-08-26
@jupiterone/data-model@0.9.0
Changelog
3.0.0 - 2020-08-24
#291 - Introduce
j1-integration document
command that is used to automatically generate
documentation in {integration-proj-dir}/docs/jupiterone.md
.
#284 - Introduce
jobState.findEntity
, which will return null
if the entity does not exist.
Example:
const entity = await jobState.findEntity('entity-key-here');
RelationshipClass
from the @jupiterone/data-model
inside of
@jupiterone/integration-sdk-core
.Usage:
import { RelationshipClass } from '@jupiterone/integration-sdk-core';
BREAKING #291 - Remove
types
from IntegrationStep
in favor of entities
and relationships
,
which contain metadata used to generate documentation.
BREAKING #285 - Require a
RelationshipClass
from @jupiterone/data-model
to be specified in
relationship creation functions.
Example:
import {
createDirectRelationship,
RelationshipClass
} from '@jupiterone/integration-sdk-core';
createDirectRelationship({
_class: RelationshipClass.HAS,
...
});