Export from GitLab to Elasticsearch
CloudQuery is an open-source data integration platform that allows you to export data from any source to any destination.
The CloudQuery GitLab plugin allows you to sync data from GitLab to any destination, including Elasticsearch. It takes only minutes to get started.
GitLab
The CloudQuery GitLab plugin pulls configuration out of GitLab resources and loads it into any supported CloudQuery destination
cloudquery
v4.3.1
Source
Mar 26, 2024
Elasticsearch
This plugin is in preview.
The Elasticsearch plugin syncs data from any CloudQuery source plugin(s) to an Elasticsearch cluster
cloudquery
v3.2.6
Destination
Mar 26, 2024
Table of Contents
MacOS Setup
Step 1. Install CloudQuery
brew install cloudquery/tap/cloudquery
Step 2. Configure GitLab source plugin
You can find more information about the configuration in the plugin documentation
kind: source
# Common source-plugin configuration
spec:
name: gitlab
path: cloudquery/gitlab
registry: cloudquery
version: "v4.3.1"
tables: ["gitlab_users"]
destinations: ["elasticsearch"]
# Gitlab specific configuration
spec:
# required
access_token: "${GITLAB_ACCESS_TOKEN}"
# optional, leave empty for GitLab SaaS
# base_url: "<INSTANCE_URL>"
Step 3. Configure Elasticsearch destination plugin
You can find more information about the configuration in the plugin documentation
kind: destination
spec:
name: elasticsearch
path: cloudquery/elasticsearch
registry: cloudquery
version: "v3.2.6"
write_mode: "overwrite-delete-stale"
spec:
# Elastic Cloud configuration parameters
cloud_id: "${ELASTICSEARCH_CLOUD_ID}"
api_key: "${ELASTICSEARCH_API_KEY}"
# Self-hosted Elasticsearch configuration parameters
# addresses: ["http://localhost:9200"]
# username: ""
# password: ""
# service_token: ""
# certificate_fingerprint: ""
# ca_cert: ""
# Optional parameters
# concurrency: 5 # default: number of CPUs
# batch_size: 1000
# batch_size_bytes: 5242880 # 5 MiB
Step 4. Run Sync
cloudquery sync gitlab.yml elasticsearch.yml