@jupiterone/integration-sdk-dev-tools
Advanced tools
Changelog
2.9.1 - 2020-08-06
deepmerge
dependency into
@jupiterone/integration-sdk-testing
package.Changelog
2.9.0 - 2020-08-05
jobState.addEntity
and jobState.addEntities
Example:
const entity = await jobState.addEntity(convertToEntity(data));
const entity2 = await jobState.addEntity(convertToOtherEntity(entity2));
await jobState.addRelationship(
convertToRelationship(entity, entity2)
);
// Or this:
await jobState.addRelationship(
convertToRelationship(
await jobState.addEntity(convertToEntity(data))
await jobState.addEntity(convertToOtherEntity(entity2))
)
);
visualize
cmd where mapped relationships did not consider
targetFilterKey
when matching entitiesvisualize
cmd where multiple nodes with the same nodeId could be
created, which causes rendering to failChangelog
2.8.0 - 2020-08-3
@jupiterone/integration-sdk-dev-tools
. See:
https://github.com/JupiterOne/sdk/issues/265Changelog
2.7.0 - 2020-08-2
Example:
expect(context.jobState.collectedEntities).toMatchGraphObjectSchema({
_class: ['Service'],
schema: {
additionalProperties: false,
properties: {
_type: { const: 'google_cloud_api_service' },
category: { const: ['infrastructure'] },
state: {
type: 'string',
enum: ['STATE_UNSPECIFIED', 'DISABLED', 'ENABLED'],
},
enabled: { type: 'boolean' },
usageRequirements: {
type: 'array',
items: { type: 'string' },
},
_rawData: {
type: 'array',
items: { type: 'object' },
}
}
});
Changelog
2.6.0 - 2020-07-28
getEntity({ _type, _key })
functionsourceEntityType
property on RelationshipMapping
createIntegrationRelationship
. Developers should use the exported
createDirectRelationship
or createMappedRelationship
functions.Changelog
2.5.0 - 2020-07-28
j1-integration visualize
added mapped relationships as dashed lines.j1-integration visualize
entities are colored by _type
.IntegrationConfig
to support asynchronous getStepStartStates
. See
#254 for more information.Example:
export const invocationConfig: IntegrationInvocationConfig<IntegrationConfig> = {
async getStepStartStates(ctx) {
return {
'fetch-users': { disabled: await checkFetchUsersStepDisabled(ctx) }
};
},
...
};
Changelog
2.3.0 - 2020-07-06
@jupiterone/data-model
to latest version (0.7.1
).@jupiterone/integration-sdk-dev-tools
did not include ts-node
, so that
yarn start
would fail to execute with 'Integration invocation configuration
not found. Configuration should be exported as "invocationConfig" from
"src/index".'Changelog
12.2.1 - 2024-03-01
Changelog
2.2.0 - 2020-06-23
publishMetric
now logs the metric that is published.Changelog
2.1.1 - 2020-06-23
validateInvocation
function will have certain types of errors it throws
(IntegrationValidationError
, IntegrationProviderAuthenticationError
)
logged at level: 40
(warn) instead of level: 50
(error). These are types
that are considered handled user errors and are expected to be communicated to
the user in a way that allows them to address the problem. All other error
types thrown from the function will continue to be logged at level: 50
.