Export from DigitalOcean to Neo4j
CloudQuery is an open-source data integration platform that allows you to export data from any source to any destination.
The CloudQuery DigitalOcean plugin allows you to sync data from DigitalOcean to any destination, including Neo4j. It takes only minutes to get started.
DigitalOcean
The CloudQuery DigitalOcean plugin pulls configuration from DigitalOcean and loads it into any supported CloudQuery destination
Neo4j
This plugin is in preview.
This destination plugin lets you sync data from a CloudQuery source to a Neo4j database
Table of Contents
MacOS Setup
Step 1. Install CloudQuery
brew install cloudquery/tap/cloudqueryStep 2. Log in to CloudQuery CLI
Logging in is required to use premium plugins and premium tables in open-core plugins.
cloudquery loginStep 3. Configure DigitalOcean source plugin
You can find more information about the configuration in the plugin documentation
kind: source
spec:
# Source spec section
name: digitalocean
path: cloudquery/digitalocean
registry: cloudquery
version: "v6.0.0"
tables: ["*"]
destinations: ["neo4j"]
spec:
# required, unless env variable DIGITALOCEAN_TOKEN or DIGITALOCEAN_ACCESS_TOKEN is set
token: "${DIGITALOCEAN_ACCESS_TOKEN}"
# Optional parameters
# spaces_regions: ["nyc3", "sfo3", "ams3", "sgp1", "fra1", "syd1"]
# spaces_access_key: ""
# spaces_access_key_id: ""
# spaces_debug_logging: false
# concurrency: 10000Step 4. Configure Neo4j destination plugin
You can find more information about the configuration in the plugin documentation
kind: destination
spec:
name: "neo4j"
path: "cloudquery/neo4j"
registry: "cloudquery"
version: "v5.1.9"
spec:
connection_string: "${NEO4J_CONNECTION_STRING}"
username: "${NEO4J_USERNAME}"
password: "${NEO4J_PASSWORD}"
# Optional parameters:
# batch_size: 1000 # 1K entries
# batch_size_bytes: 4194304 # 4 MiBStep 5. Run Sync
cloudquery sync digitalocean.yml neo4j.yml