Documentation
Reference
Source Spec Reference

Source Spec Reference

Following are available options for the top level source plugin spec object.

Note: For configuring individual plugins, please refer to the configuration section from the relevant plugins from here (opens in a new tab). (e.g. AWS plugin configuration (opens in a new tab)).

Example

This example configures the AWS plugin, and connects is to a postgresql destination:

kind: source
spec:
  name: "aws"
  path: "cloudquery/aws"
  registry: "cloudquery"
  version: "v27.4.0"
  tables: ["aws_s3_buckets"]
  destinations: ["postgresql"]

  spec:

Spec

name

(string, required)

Name of the plugin. If you have multiple source plugins, this must be unique.

The name field may be used to uniquely identify a particular source configuration. For example, if you have two configs for the AWS plugin for syncing different accounts, one may be named aws-account-1 and the other aws-account-2. In this case, the path option below must be used to specify the download path for the plugin.

registry

(string, optional, default: cloudquery, available: github, cloudquery, local, grpc, docker)

  • cloudquery: CloudQuery will look for and download the plugin from the official CloudQuery registry, and then execute it.
  • github: Deprecated. CloudQuery will look for and download the plugin from GitHub, and then execute it.
  • local: CloudQuery will execute the plugin from a local path.
  • grpc: mostly useful in debug mode when plugin is already running in a different terminal, CloudQuery will connect to the gRPC plugin server directly without spawning the process.
  • docker: CloudQuery will run the plugin in a Docker container. This is most useful for plugins written in Python, as they do not support the local, github and cloudquery registries.

docker_registry_auth_token

(string, optional, default: "", introduced in CLI v5.7.0)

Authentication token for private Docker container registries. This is required if the plugin is hosted in a private Docker container registry. The token should be a valid Docker registry token that can be used to pull the plugin image. This option is only relevant when registry is set to docker. The token is a base64 encoded string. Here is an example of how to generate the token:

echo -n "{\"username\":\"<REPLACE_WITH_PASSWORD>\",\"password\":\"<REPLACE_WITH_PASSWORD>\"}" | base64`

Details about specific private container registries:

AWS ECR: The username is AWS and you can get the password by running aws ecr get-login-password --region <region>. Replace <region> with the region where the ECR is located.

Generating the token for AWS ECR would look like this:

echo -n "{\"username\":\"AWS\",\"password\":\"$(aws ecr get-login-password --region <REGION>)\"}" | base64

GitHub Container Registry: The username is USERNAME and you use a personal access token as the password. More information can be found here (opens in a new tab)

Generating the token for GitHub Container Registry would look like this:

export CR_PAT=YOUR_TOKEN
echo -n "{\"username\":\"USERNAME\",\"password\":\"$CR_PAT\"}" | base64

path

(string, required)

Configures how to retrieve the plugin. The contents depend on the value of registry (github by default).

  • For plugins hosted on GitHub, path should be of the form "<org>/<repository>". For official plugins, should be cloudquery/<plugin-name>.
  • For plugins that are located in the local filesystem, path should a filesystem path to the plugin binary.
  • To connect to a running plugin via grpc (mostly useful for debugging), path should be the host-port of the plugin (e.g. localhost:7777).
  • For plugins distributed via Docker, path should be the name of the Docker image (optionally including a tag, the same as you would use for docker run, e.g. ghcr.io/cloudquery/cq-source-typeform:v1.0.0).

version

(string, required)

version must be a valid SemVer (opens in a new tab)), e.g. vMajor.Minor.Patch. You can find all official plugin versions under cloudquery/cloudquery/releases (opens in a new tab), and for community plugins you can find it in the relevant community repository. This is only relevant for plugins hosted on GitHub.

tables

([]string, required)

This option was changed to required in versions >= v3.0.0 of the CloudQuery CLI. In previous versions it was optional and defaulted to ["*"] (sync all tables).

Tables to sync from the source plugin. It accepts wildcards. For example, to match all tables use ["*"] and to match all EC2-related tables use aws_ec2_*. Matched tables will also sync all their descendant tables, unless these are skipped in skip_tables. Please note that syncing all tables can be slow on some plugins (e.g. AWS, GCP, Azure).

skip_tables

([]string, optional, default: [])

Specify which tables to skip when syncing the source plugin. It accepts wildcards. This config is useful when using wildcards in tables, or when you wish to skip dependent tables. Note that if a table with dependencies is skipped, all its dependent tables will also be skipped.

skip_dependent_tables

(bool, optional, default: false, introduced in CLI v2.3.7)

If set to true, tables that depend on the tables specified in tables will not be synced, unless specifically selected themselves. This allows you to choose precisely which tables to sync, and prevents automatically syncing new dependent tables that may be added to the plugin in future versions. Note that if you specify a table that depends on another table, CloudQuery will still automatically include the parent table(s).

destinations

([]string, required)

Specify the names of the destinations to sync the data of the source plugin to.

deterministic_cq_id

(bool, optional, default: false, introduced in CLI v2.4.1)

A flag that indicates whether the value of _cq_id should be a UUID that is a hash of the primary keys or a random UUID. If a resource has no primary keys defined the value will always be a random UUID. This option cannot be used when you are using a destination that enforces primary keys in append write mode as the _cq_id needs to be unique for each row.

Supported by source plugins released on 2023-03-08 and later

otel_endpoint (preview)

(string, optional, introduced in CLI v3.10.0)

Open Telemetry OTLP/HTTP (opens in a new tab) exporter. Also, supports Jaeger endpoint. This will send traces of syncs to that endpoint.

otel_endpoint_insecure (preview)

(bool, optional, default: false, introduced in CLI v3.10.0)

If set to true, the exporter will not verify the server will connect via http instead of https.

spec

(object, optional)

Plugin-specific configurations. Visit source plugins (opens in a new tab) documentation for more information.

Top level deprecated options

concurrency

This option was deprecated in CLI v3.6.0 in favor of plugin level concurrency, as each plugin as its own concurrency requirements. See more in each plugin documentation.

scheduler

This option was deprecated in CLI v3.6.0 in favor of plugin level scheduler, as each plugin as its own scheduler requirements. See more in each plugin documentation.

backend

This option was deprecated in CLI v3.6.0 in favor of backend_options. See Managing Incremental Tables for more information.

backend_spec

This option was deprecated in CLI v3.6.0 in favor of backend_options. See Managing Incremental Tables for more information.

Setting spending limitsDestination Spec Reference