You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- delete: add IsAlreadyDeleted idempotency branch so `slos delete --force`
on an already-deleted SLO exits 0 (matches the 8 other delete commands,
CHANGELOG 1.16.2 / #217); cover with an integration test.
- update: StripSLOServerFields before the dry-run diff and PUT so
`get -o yaml | update -f` no longer sends server-managed labels/timestamps
or shows a spurious diff (mirrors views/update.go).
- asset/ImportSLO: mirror ImportTeam upsert-key selection — prefer
dash0.com/id, fall back to dash0.com/origin (read before strip), POST only
when neither is present, so an origin-only document upserts via PUT instead
of duplicating on every apply (#227 shape).
- list: replace interface{} with any on the column closures (matches
views/list.go).
- integration tests: assert the update wire body strips dash0.com/version,
dash0.com/origin, and created-at; add create/update --dry-run tests; add a
second element to list_success.json and exercise --limit truncation.
- roundtrip: add test_apply_slo_idempotency.sh (double-apply, no duplicate /
stable id) and register it in run_all.sh.
- docs: add teams to the command-group enumerations in commands.md and
cli-naming-conventions.md and adjust the count wording.
- Use **kebab-case** for multi-word names: `check-rules`, `synthetic-checks`, `recording-rules`, `notification-channels`, `spam-filters`
10
10
- Group related functionality: `config profiles` for profile management
11
11
12
12
## Standard CRUD Subcommands for Assets
13
-
All asset commands (`dashboards`, `check-rules`, `views`, `synthetic-checks`, `slos`, `recording-rules`, `notification-channels`, `spam-filters`) use these subcommands:
13
+
All asset commands (`dashboards`, `check-rules`, `views`, `synthetic-checks`, `slos`, `recording-rules`, `notification-channels`, `spam-filters`), along with the organization-level `teams` command, use these subcommands:
Dash0 calls dashboards, views, synthetic checks, and check rules "assets" (not "resources", which is an overloaded term in OpenTelemetry).
496
496
497
-
All eight asset types (`dashboards`, `check-rules`, `synthetic-checks`, `slos`, `views`, `recording-rules`, `notification-channels`, `spam-filters`) share the same CRUD subcommands.
498
-
The examples below use `dashboards`, but the same patterns apply to every asset type.
497
+
All nine of these command groups (`dashboards`, `check-rules`, `synthetic-checks`, `slos`, `views`, `recording-rules`, `notification-channels`, `spam-filters`, and the organization-level `teams`) share the same CRUD subcommands.
498
+
The first eight are dataset-scoped assets;`teams` is organization-level (no `--dataset`, no `apply`) but shares the same subcommand shape.
499
+
The examples below use `dashboards`, but the same patterns apply to every command group.
0 commit comments