Adam Williams

> from multiple collectors/steps I see there is just a [single step](https://github.com/JupiterOne/graph-qualys/blob/master/src/steps/collect-data.ts) right now. Did you do it that way because there is no way to share data across steps?...

@philidem hadn't we thought to pursue key uniqueness even across entities and relationships? Or, are we forever stuck with a compound key? What is the compound key then? It must...

I think it still a good idea to have a JSON Schema for the config, but now that we have moved projects to `integrationConfigFields.ts`, we'd likely want to generate the...

Goals: * Avoid exposing steps in the selection UI * Perhaps categorize steps so that the UI shows the categories as options (EC2, IAM) * Keep integration simple, support new...

I also like the approach of having a single `index.ts` file that pulls together everything and is the one place to find the step meta data. 👍 @charlieduong94 has mentioned...

> Thoughts on maybe defining dependencies as a something like `Record` where the property name is the step id and the array is the list of dependencies? Do you mean,...

@ndowmon I'd like to clarify goals and non goals: 1. Non-goal: Avoid relationships for obtaining properties in a query/question. 2. Goal: Support ingesting rules for host-based firewalls, where there is...

Discussion IRL... It has been suggested that the `_type` value should be `user_endpoint` ONLY IF there is ample data in the Snipe-IT asset to determine that it is in fact...

I agree, that constraint should be removed. We should be able to count on the the combination of `_type` and `_key` (scope, really) to prevent duplicates, as the key tracker...

To clarify, is this the acceptance criteria you're suggesting? - [ ] Allow `` characters in `webLink` values - [ ] Allow any URI scheme value, including everything listed at...