Nick Dowmon
Nick Dowmon
It seems that the `awsV4Signature()` function is loaded as an axios request interceptor in `@lifeomic/alpha`, which (I think) means that the function is invoked on each request. Since a new...
Recently, we encountered an integration where a single step that calls `jobState.iterateEntities()` took multiple hours to execute. Since this step is sequentially reading from disk, waiting for network calls, and...
> Awesome! Would you mind adding this to the development documentation please? I'd also love to see a task created to update the `integration-template`! I'd like to make some minor...
More so for curiousity but we have the ability to create multiple dependency graphs. Have you tried to run that use case/does your code account for that? Maybe something we...
Would love to see a ticket in the SDK describing this! _Originally posted by @austinkelleher in https://github.com/JupiterOne/sdk/pull/611#discussion_r803787925_
As we move closer to specification-defined integrations, I propose adding an optional `schema` property to the `StepEntityMetadata` and `StepRelationshipMetadata` interfaces. This `schema` can be used in: 1. conversion tests (`expect(entities).toMatchGraphObjectSchema({...
I would love to see the package/version printed out in the job log: ```shell (10:50:08 AM) - [job_start] - Job for integration Azure has started. (10:50:08 AM) - [version] -...
We should be continuously driving towards improving our dependency execution graph. We have some integrations that require multiple permissions to execute, and we should add these requirements to step metadata...
Currently, if we have multiple `rawData` sets added to an entity, we need to use the `setRawData` function after creating an entity: ```typescript const entity = createIntegrationEntity({ entityData: { source:...
Virtually every resource we create is fetched from an API. I think the API endpoint provides valuable context about the raw data associated with an entity (or relationship). Given we...