The V(ector) Dev(elopment) tool.

This is the command line tooling for Vector development. You don't need to use or install this unless you are doing development in the Vector repo.

Table of Contents:

• Pre-requisites
• Installation
• Running Tests
  • Running Integration tests
• Developing vdev

This assumes that you have the following tools installed:

• git
• cargo
• docker
• npm

Some other tools may need to be installed depending on the command you are running. All other dependencies can be installed by running

./scripts/environment/prepare.sh

CI installs vdev from a published binary release via cargo-binstall and never builds it from source. To match that locally:

./scripts/environment/prepare.sh --modules=vdev

This pins the vdev version defined in prepare.sh and fetches the matching pre-compiled binary.

For a quick install of the latest published vdev (not pinned):

cargo binstall vdev

If binstall is unavailable, fall back to compiling from crates.io:

cargo install vdev

Installation is otherwise optional: from within the Vector repository, cargo vdev works via a cargo alias that compiles vdev from source on each invocation. That path is fine for occasional use but is slower than a binstalled binary.

Unit tests can be run by calling make test.

Integration tests require docker or podman to run.

Integration tests are not run by default when running make test. Instead, they are accessible via the integration subcommand cargo vdev int (example: cargo vdev int test aws runs aws-related integration tests).

You should use ./scripts/run-integration-test.sh, which is the wrapper used by CI and which suits most development needs. Integration tests require a cargo vdev int start, cargo vdev int test, and cargo vdev int stop, which the script handles automatically. You can find the list of available integration tests using cargo vdev int show.

If you are actively developing vdev itself, install from your working tree so the binary on PATH reflects your local changes:

cargo install -f --path vdev

The CLI uses Clap with the derive construction mechanism and is stored in the commands directory.

Every command group/namespace has its own directory with a cli module, including the root vdev command group. All commands have an exec method that provides the actual implementation, which in the case of command groups will be calling sub-commands.