vdev 0.3.11

CLI utilities for Vector (vector.dev) development and CI workflows
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

use anyhow::Result;
use clap::Args;

use crate::testing::integration::ComposeTestLocalConfig;

/// Run a complete integration test workflow (CI-style)
///
/// This command orchestrates the full integration test lifecycle:
/// 1. Clean up previous test output
/// 2. Start the environment
/// 3. Run tests with retries
/// 4. Upload results to Datadog (in CI)
/// 5. Stop the environment (always, as cleanup)
///
/// This is useful for CI workflows and local testing that mimics CI behavior.
#[derive(Args, Debug)]
#[command()]
pub struct Cli {
    /// The integration name
    test_name: String,

    /// The desired environment name(s) to run. If omitted, all environments are run.
    /// Can be specified multiple times or comma-separated.
    #[arg(short = 'e', long = "environment", value_delimiter = ',')]
    environments: Vec<String>,

    /// Number of retries for the test phase
    #[arg(short = 'r', long, default_value = "2")]
    retries: u8,

    /// Collect code coverage using cargo-llvm-cov (outputs target/coverage/lcov.info)
    #[arg(long)]
    coverage: bool,

    /// Always print docker compose logs, even on success (logs are always printed on failure regardless)
    #[arg(long)]
    always_show_logs: bool,
}

impl Cli {
    pub fn exec(self) -> Result<()> {
        crate::commands::compose_tests::run::exec(
            ComposeTestLocalConfig::integration(),
            &self.test_name,
            &self.environments,
            self.retries,
            self.coverage,
            self.always_show_logs,
        )
    }
}