Usage
vg push [--dsn <dsn>] [--file <file>] [--region <region>] [--strict]
What It Does
vg push uploads a scan artifact to the Vibgrate Cloud API. This gives teams a shared view of drift across projects, historical trend charts, and portfolio-level risk assessment.
Upload is always optional. The CLI provides full value locally without any server connection.
Flags
| Flag | Default | Description |
|---|---|---|
--dsn | VIBGRATE_DSN env | DSN token for authentication |
--file | .vibgrate/scan_result.json | Scan artifact to upload |
--region | — | Override data residency region (us, eu) |
--strict | — | Fail hard on upload errors |
DSN Authentication
Vibgrate uses HMAC-signed DSN tokens. The format:
vibgrate+https://<key_id>:<secret>@<ingest_host>/<workspace_id>
Set VIBGRATE_DSN as a secret in your CI environment:
env:
VIBGRATE_DSN: ${{ secrets.VIBGRATE_DSN }}Data Residency
| Region | Endpoint |
|---|---|
| US (default) | us.ingest.vibgrate.com |
| EU | eu.ingest.vibgrate.com |
Use --region eu to route data to the EU endpoint.
Examples
Basic push
vg push
Push with explicit DSN
vg push --dsn "vibgrate+https://key:secret@us.ingest.vibgrate.com/ws-123"
Strict mode in CI
vg push --strict --file .vibgrate/scan_result.json
EU data residency
vg push --region eu
Best Practices
- Use
--strictin CI if you want pipelines to fail on upload errors - Without
--strict, push is best-effort — upload failures are logged but do not affect exit codes - Store your DSN as a CI secret, never in source code
- Add
.vibgrate/scan_result.jsonto.gitignore