## Overview `dibble` is a one-stop CLI for seeding a Fleet server with test data — users, teams, policies, reports, labels, scripts, MDM profiles, software, secrets, CAs, and vulns — replacing ~8 ad-hoc seeding tools with a single binary. It makes it easy to: - **Spin up a populated dev/test server in one command** — `dibble all` plants everything with sensible, idempotent defaults. - **Skip the flag-memorization** — running `dibble` with no args launches an interactive wizard that prompts for Fleet URL, API token, theme, and which entities to seed, and offers to save the config to `~/.dibble.yaml`. - **Seed individual entity types** — `dibble users`, `dibble teams`, `dibble policies`, etc., when you only need one slice. - **Get themed, recognizable test data** — pick a theme (hitchhikers, tng, lotr, ghibli, parksrec, …) so seeded names are easy to eyeball in the UI. Hosts are intentionally out of scope — `cmd/osquery-perf` still owns that. `dibble hosts` is a thin convenience wrapper that picks a fleet, fetches its enroll secret, and prints/runs the osquery-perf invocation for you. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Dibble: a CLI tool to seed realistic test data, including an interactive wizard and subcommands for teams/users/software/policies/scripts/reports/profiles/labels/activities/enroll-secrets/hosts/vulns, plus theme-driven “cas” and “ping”. * Theme system: multiple curated themes to generate consistent seeded identities, policies, software, labels, and scripts. * **Chores** * Ignored the built dibble binary and added a Makefile build target to compile the dibble tool. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
866 B
866 B
Note
Prefer
dibblefor seeding scripts and MDM profiles. The equivalents are:./tools/dibble/dibble scripts --count N ./tools/dibble/dibble profiles --count NThis tool is kept for backwards compatibility. We'll remove it once nothing references it.
scripts_and_profiles
Go program used to load-test scripts and MDM profiles for the unified queue story.
It creates team_count teams and attaches a fixed set of scripts and MDM
profiles (Apple + Windows) to each, exercising the scripts/profile distribution
pipeline at scale.
Usage
go run ./tools/loadtest/scripts_and_profiles \
-fleet_url https://localhost:8080 \
-api_token "$FLEET_API_TOKEN" \
-team_count 20
Add -cleanup_teams to delete the created teams after the run.