Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/jupiterone/graph-atspoke
A graph conversion tool for https://atspoke.com
https://github.com/jupiterone/graph-atspoke
Last synced: 7 days ago
JSON representation
A graph conversion tool for https://atspoke.com
- Host: GitHub
- URL: https://github.com/jupiterone/graph-atspoke
- Owner: JupiterOne
- License: mpl-2.0
- Created: 2021-02-16T12:39:22.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2023-12-05T17:50:12.000Z (11 months ago)
- Last Synced: 2023-12-05T18:50:44.839Z (11 months ago)
- Language: TypeScript
- Size: 160 KB
- Stars: 0
- Watchers: 14
- Forks: 4
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
- Codeowners: CODEOWNERS
Awesome Lists containing this project
README
# JupiterOne Integration
Learn about the data ingested, benefits of this integration, and how to use it
with JupiterOne in the [integration documentation](docs/jupiterone.md).## Development
### Prerequisites
1. Install [Node.js](https://nodejs.org/) using the
[installer](https://nodejs.org/en/download/) or a version manager such as
[nvm](https://github.com/nvm-sh/nvm) or [fnm](https://github.com/Schniz/fnm).
2. Install [`yarn`](https://yarnpkg.com/getting-started/install) or
[`npm`](https://github.com/npm/cli#installation) to install dependencies.
3. Install dependencies with `yarn install`.
4. Register an account in the system this integration targets for ingestion and
obtain API credentials.
5. `cp .env.example .env` and add necessary values for runtime configuration.When an integration executes, it needs API credentials and any other
configuration parameters necessary for fetching data from the provider. The
names of these parameters are defined in `src/instanceConfigFields.ts`. When
executed in a development environment, values for these parameters are read
from Node's `process.env`, loaded from `.env`. That file has been added to
`.gitignore` to avoid commiting credentials.### Running the integration
1. `yarn start` to collect data
2. `yarn graph` to show a visualization of the collected data
3. `yarn j1-integration -h` for additional commands### Making Contributions
Start by taking a look at the source code. The integration is basically a set of
functions called steps, each of which ingests a collection of resources and
relationships. The goal is to limit each step to as few resource types as
possible so that should the ingestion of one type of data fail, it does not
necessarily prevent the ingestion of other, unrelated data. That should be
enough information to allow you to get started coding!See the
[SDK development documentation](https://github.com/JupiterOne/sdk/blob/master/docs/integrations/development.md)
for a deep dive into the mechanics of how integrations work.See [docs/development.md](docs/development.md) for any additional details about
developing this integration.### Changelog
The history of this integration's development can be viewed at
[CHANGELOG.md](CHANGELOG.md).